A new and improved Twitter API
blog.twitter.com
A new and improved Twitter API
1–10 of 116 posts
Re: A new and improved Twitter API
#2Lol!
We don’t trust you.
Re: A new and improved Twitter API
#3> given the security incident we discovered yesterday
We discovered. Heh.
Re: A new and improved Twitter API
#4Knowing Twitter I imagine "improved" means more closed and with stricter rate limits.
Re: A new and improved Twitter API
#5Here's there actual roadmap: https://trello.com/b/myf7rKwV/twitter-developer-platform-roa...
Re: A new and improved Twitter API
#6No word on the most important thing: the limits.
Current limits that keep becoming stricter and stricter make the API unusable.
Re: A new and improved Twitter API
#7> Eventually, the new API will fully replace the v1.1 standard, premium, and enterprise APIs.
Uh oh. Using nitter's [1] RSS feeds is one of my main ways to access news. I have the feeling this is about to end.
Re: A new and improved Twitter API
#8Knowing Twitter I imagine "improved" means more closed and with stricter rate limits.
For the free tier, the user endpoint users/lookup which now is just /users seems to maintain the same rate limit, and looking at the other endpoints I haven't seen something stand out as strongly reduced.
I notice that there doesn't seems to be a distinction in the new API between user context and app context as far as rate limiting is concerned, so maybe that would make a difference.
But a lot of endpoints are still missing so everything is still to see!
Re: A new and improved Twitter API
#9[deleted]
Re: A new and improved Twitter API
#10No word on the most important thing: the limits. Current limits that keep becoming stricter and stricter make the API unusable.
Limit is your wallet