Live data from Hacker News

A new and improved Twitter API

blog.twitter.com

91–100 of 116 posts

Re: A new and improved Twitter API

#92

This is what they cite as the key benefits: "A cleaner API that's easier to use, with new developer features like the ability to specify which fields get returned, or retrieve more Tweets from a conversation within the same response Some of the most requested features that were missing from the API, including conversation threading, poll results in Tweets, pinned Tweets on profiles, spam filtering, and a more powerfu…

> conversation threading Actually, this was a major point of API failure when I last tried to use it. Did you know that, with the current API, there's no way to retrieve the replies to a tweet ? This makes it impossible to build tools that, say, allow you to visualize a tweet thread, because you simply can't fetch the thread. So I'll say that, as a casual, social, and informational user of Twitter (i.e. not business,…

Conversation threading is huge. I've had to use a few tools that keep getting broke to try to manually capture replies and threads to tweets for academic use. (https://www.exquisitetweets.com/ and https://treeverse.app/ which seems broken now)If a tool comes out that can do this easily (I'm no programmer so command line stuff if a little beyond me) then I will be very happy.

Re: A new and improved Twitter API

#94

Earlier quoted context omitted.

> This makes it impossible to build tools that, say, allow you to visualize a tweet thread it is possible -- it unfortunately happens to be part of my job description to do so one of the sibling comments basically has it right. you can build it from the bottom up (where "bottom" is the deepest tweet in the thread you know about, one way or another). let me tell you though, i am _very_ excited for this new API, becaus…

Is your work open source/viewable anywhere? I've written a few (probably ToS violating) plugins for Twitter myself, and would be curious to see.

unfortunately not, but luckily with this new api it shouldn't matter for too much longer :-)

Re: A new and improved Twitter API

#95

Earlier quoted context omitted.

Just out of curiosity: What type of application would have you interace with twitter at all? For ad purposes, some form of analysis? News aggregation?

Product support ticket systems use twitter and other social media sites to respond to customer feedback, as well as track and escalate issues. When you tweet complaints about your service at Comcast, there's probably a ticket created that someone from their support staff picks up. I think there's a perception that the quicker responses that these tools facilitate can help prevent negative feedback from going viral an…

Right. And so, for those CRMs it is vital to not just catch the first tweet. Being able to catch a thread is important to catch the rant on the third tweet in a thread that explains the exact problem.

Re: A new and improved Twitter API

#96
post #56

Earlier quoted context omitted.

If you delete the first 3600 tweets, the next 3600 should now be the latest posted.

You're technically right, but the Twitter API won't return the next 3600, even after deleting the first ones. The response will be empty, even if you know for sure there's more.

Meaning the API is leaking the number of deleted tweets?

Could you make a tool to find out how many tweets someone has deleted?

Re: A new and improved Twitter API

#98

Earlier quoted context omitted.

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.

The way clients usually do this is by fetching all mentions to the user after a given timestamp (of the original tweet), and collecting only those that are replies to the tweet. Since there's a limit on how many mentions you can get, you might not get all the replies.

It's been like that at least since 2013.

Re: A new and improved Twitter API

#99

Earlier quoted context omitted.

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…

Are you getting the prices from this [0] page? I think that's the pricing for the old API, because it still hast the standard/premium/enterprise split.

> In the past, the Twitter API was separated into three different platforms and experiences: standard (free), premium (self-serve paid), and enterprise (custom paid). As a developer's needs expanded, it required tedious migration to each API. In the future, all developers — from academic researchers to makers to businesses — will have options to get elevated access and grow on the same API. > (https://blog.twitter.com/developer/en_us/topics/tools/2020/i...)

[0] https://developer.twitter.com/en/pricing

Re: A new and improved Twitter API

#100

No word on the most important thing: the limits. Current limits that keep becoming stricter and stricter make the API unusable.

That's what killed off Falcon Pro. The author released a version of the APP with a secret way of putting in your own API keys and I used that for a bit. Then he released a new version, but couldn't just grant the old people access because it would quickly reach the rate limit. It was about that time I just totally abandoned Twitter. Use Mastodon/Pleroma/Misskey. Fuck lock-ins. ActivyPub forever!

I don't understand what is the issue if user can add their own keys - just release the app with default set of keys or even without and let the user set their own.

Other than that, indeed Mastodon and co. are great. :)

Post reply on HN