Crazy-Duck

I haven't checked the protobufs in a while so don't know where the client is getting the MVP info. But I'd say NetHooking the client like Howard is suggesting is...

You're going to have to use the hacky way, since extended_entities still aren't supported by the twitter API. See [here](https://twittercommunity.com/t/search-tweets-endpoint-and-extended-entities/31655)

For the target wav, do you have recommendations as to the length? Does performance of the model improve/deteriorate with longer target wavs? If so, where's the sweet spot?