- [x] ~Decide on the OAuth 2.0 client library to use (or extend [tesaguri/oauth1-request-rs](https://github.com/tesaguri/oauth1-request-rs) to support it)~ - What Twitter calls "OAuth 2.0" seems to use the access token type of "bearer" only, which is trivial enough to just implement in `twitter_stream`. - [ ] Implement APIs ~behind an unstable feature flag~ - [ ] Filter - [ ] Sample - [ ] ~Stabilize the new APIs and deprecate the current APIs after the new endpoints graduate out of Labs~ - [ ] Remove the existing APIs after the current endpoints is closed ## Links - ["New filtered stream endpoints available in Labs, and the future of statuses/filter - Announcements - Twitter Developers"](https://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888) - ["New sampled stream endpoint available in Labs - Announcements - Twitter Developers"](https://twittercommunity.com/t/new-sampled-stream-endpoint-available-in-labs/130958) - [Twitter Developers docs on the new filtered stream](https://developer.twitter.com/en/docs/labs/filtered-stream/overview) - [Twitter Developers docs on the new sampled stream](https://developer.twitter.com/en/docs/labs/sampled-stream/overview)
Decide on the OAuth 2.0 client library to use (or extend tesaguri/oauth1-request-rs to support it)twitter_stream.behind an unstable feature flagStabilize the new APIs and deprecate the current APIs after the new endpoints graduate out of LabsLinks