Notice the page never seems to mention 3rd party clients, the only thing many of us care about.
A new and improved Twitter API
81–90 of 116 posts
Re: A new and improved Twitter API
#82I ran a Twitter app for 9 years that they crippled, crippled, then eventually killed with policies. It went from “@ev loves your app,” to “your app is against our terms of service” in that time. My Twitter days are done.
Re: A new and improved Twitter API
#83Did anyone look at the prices?? Holy shit. Are they selling gold? Those prices are ridiculous.
Where do you find the prices?
Re: A new and improved Twitter API
#84Earlier quoted context omitted.
You have to use the search feature to look for tweets and then look at the parent tweet ID. This is what bots like threadreaderapp, etc do. You can construct it from the bottom up if you know the ID of the last tweet in the thread of responses too, but you wouldn't know that a priori unless the user gives it to your software somehow.
But... that's not a tree -- there's still no way to discover all leaves. That's just a thread/singly linked list.
Yes, I forgot to mention that. You need to know the IDs of all the leaf nodes of the thread or else you can only partially reconstruct it.
Re: A new and improved Twitter API
#85[deleted]
Re: A new and improved Twitter API
#86Did anyone look at the prices?? Holy shit. Are they selling gold? Those prices are ridiculous.
Where do you find the prices?
When you login with the Developer account it gives you an option to upgrade and there you can see the prices. But I'll save you that: 2500 requests against their Full Archive costs 1899 USD. That's 75 cents per request.
That sounds absurd to me. 2500 requests is nothing and what if you're testing? The sandbox level is 50 requests for free.
Maybe I don't understand well the use cases but all the things that come to my mind for these APIs would required more than 2500 requests to do something interesting. They are pricing their data like if it was some sort of unique canonical truth vault when in reality 95% of it, it's just a bunch of shitposts.
Re: A new and improved Twitter API
#87It doesn't answer the most important question: is it OAuth2 now?
Re: A new and improved Twitter API
#88Earlier quoted context omitted.
> there's no way to retrieve the replies to a tweet My crusty old version of Tweetbot has been doing that for years...? Maybe not perfectly for tweets with hundreds of replies, but well enough.
I'm not sure which hack Tweetbot is using to do this (I think search as noted below), but you can tell it's a hack because it only works for recent-ish tweets. If you go to a tweet a couple weeks old and view details, you can see that it won't fill in the replies.
Can confirm, Tweetbot never has "all" the replies.
Re: A new and improved Twitter API
#89Nobody wants a new API. The new features don’t make up for all the work needed to rewrite every call. Again. Nobody wants this.
As a user I would like for Twitterrific for example to support polls and pinned tweets. So at least one user of a third partly client wants this, I bet that there are more.
Re: A new and improved Twitter API
#90I ran a Twitter app for 9 years that they crippled, crippled, then eventually killed with policies. It went from “@ev loves your app,” to “your app is against our terms of service” in that time. My Twitter days are done.
Have you written about your experience? I'd just be curious to know what you built, and the series of the events that unfolded.