Matthew R. DeVerna

Thanks for opening this @andypiper! Any chance we'll see this in the (relatively) near future? 😄 Hoping to include some of this functionality in a [Twitter V2 python package](https://github.com/osome-iu/osometweet) (aimed...

Thanks, @igorbrigadir — you are truly a legend... ❤️ @yangkcatiu I'll let you make the call about whether or not to add the additional optional fields as I suspect you...

See #95 to track these regardless of whether they are all added or not. Thanks!

**Note: The temporary solution for this problem is simply to authorize your `bearer_token` with `manage_rate_limits=False`**. For example, see the [streaming wiki page](https://github.com/osome-iu/osometweet/wiki/Method:-Streaming#adding-filter-rules) for an example. This works because setting it...

Update: The streaming endpoints now throw an error if you try to use them without the above-mentioned solution in place.

That's a good point. Probably it's best to keep things a bit more bare-bones. I think this issue is super low-priority, it was just something that popped into my head...

So it seems like a good general rule would be: _**non-essential/extra features should be kept out of the core library**_. This sounds like the best of both worlds to me....

> This is very things get complicated. I agree. I don't think that we need all of these but probably we do need to deal with the low data volumes...

Awesome, thanks! I'll post updates on this issue.

Update... - Streaming examples (filtered and sample) will be included in #75 - Timeline examples (tweets and mentions) will be included in #82