-
Notifications
You must be signed in to change notification settings - Fork 57
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
twitter v2 API #136
Comments
in the meantime, i should add a louder warning to the granary docs and UI that twitter search is just the last week, and not comprehensive. |
for granary.io at least, this is pretty unlikely. the premium API costs $0.25-$1/request/month, depending on volume and endpoint (30d vs full history), and the free tier is limited to 50-250 requests/month. so, not really an option. |
New announcement and launch of the v2 API today. Promising:
Notably, the intro tier ("Essential") doesn't require approval at all any more, and they've dropped many of the approval requirements, including the limits on replicating Twitter's UX. Huge! The rate limits are still too small for Bridgy, though. The Essential tier is 1.7qpm, Elevated is 3.3qpm, Bridgy averages 30-60qpm. |
Started on this! |
#136, https://developer.twitter.com/en/docs/twitter-api this migrates tweet_to_object(), tweet_to_activity(), and some initial tests. lots more to do.
#136, https://developer.twitter.com/en/docs/twitter-api this migrates tweet_to_object(), tweet_to_activity(), and some initial tests. lots more to do.
#136, https://developer.twitter.com/en/docs/twitter-api this migrates tweet_to_object(), tweet_to_activity(), and some initial tests. lots more to do.
#136, https://developer.twitter.com/en/docs/twitter-api this migrates tweet_to_object(), tweet_to_activity(), and some initial tests. lots more to do.
Deprioritized due to all the Twitter acquisition chaos. |
^ this is now entirely dependent on snarfed/bridgy#1410. Not looking good. |
Twitter is now developer-hostile, so I don't plan to work on this myself. I'll happily review and merge PR(s) though! |
Closing; granary's Twitter support may be on the road to deprecation. |
we currently use twitter's existing (legacy? :P) search API that "searches against a sampling of recent Tweets published in the past 7 days." this confused @aaronpk when he searched for
streampdx
, and got no results since they're all over 7d old.twitter just launched their new premium search API, which includes full history! both paid and free tiers.
...except you have to ask permission, tell them what you're building, and get approved. :( i can't tell if that's just because it's in beta right now, or permanent.
Good news is, I went through that approval process recently with a test account, and it went fine. Plus, the intro tier ("Essential") doesn't require approval at all any more, and they've dropped many of the approval requirements, including the limits on replicating Twitter's UX. Huge!
Missing features
These are blocking migrating Bridgy at least, if not granary:
conversation_id
is awesome, but it's always based on a top-level tweet, and we need to be able to fetch replies to any tweet, including replies themselves, which the v2 API can't do yet, and I'm not holding my breath. 😐The text was updated successfully, but these errors were encountered: