Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filtered Streams support - is it ready? #1283

Closed
NetwarSystem opened this issue Oct 21, 2019 · 2 comments
Closed

Filtered Streams support - is it ready? #1283

NetwarSystem opened this issue Oct 21, 2019 · 2 comments
Labels
API This is regarding Twitter's API Feature This is regarding a new feature Improvement This is regarding an improvement to an existing feature Question This is a question RFC This is a Request For Comments

Comments

@NetwarSystem
Copy link

I just noticed Andy Piper announcing the sunsetting of the current streaming methods:

https://twitter.com/andypiper/status/1186325788813119488

And I have not dug into this yet:

https://developer.twitter.com/en/docs/labs/filtered-stream/overview

Where does Tweepy development stand in terms of these upcoming changes?

@Harmon758
Copy link
Member

Filtered Stream was only added to Labs a month ago, and there's no deprecation date for the statuses/filter and statuses/sample endpoints yet:

With today’s announcement, we are also letting you know about the future deprecation of the current statuses/filter endpoint available through our current API. Once the filtered stream endpoints graduate out of Labs, they will replace the statuses/filter endpoint you use today. At that point, we will give 6 months’ notice to provide necessary time to transition. We plan to follow a similar pattern for our existing GET statuses/sample endpoint, as well.

See https://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888.

I definitely plan on adding support for the filtered stream endpoints once they become part of the standard API. As of right now, I'm undecided on whether or not to support features in Labs, as it would require extra dev and maintenance work for features that aren't stable/generally released yet. Even if the decision was made to do so, it would likely come after version 3.9 and 4.0, as those releases will likely include large features in the standard API that are currently unsupported (see the associated milestones; support for the Account Activity API might also be included in version 4.0).

@Harmon758 Harmon758 added API This is regarding Twitter's API Feature This is regarding a new feature Improvement This is regarding an improvement to an existing feature Question This is a question RFC This is a Request For Comments labels Oct 22, 2019
@Harmon758
Copy link
Member

Closing this in favor of #1472 now, since the Labs version of filtered stream has been graduated (and retired) into Twitter API v2 as the filtered stream endpoint group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API This is regarding Twitter's API Feature This is regarding a new feature Improvement This is regarding an improvement to an existing feature Question This is a question RFC This is a Request For Comments
Projects
None yet
Development

No branches or pull requests

2 participants