Live data from Hacker News

A new and improved Twitter API

blog.twitter.com

61–70 of 116 posts

Re: A new and improved Twitter API

#62
post #41

Earlier 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.

Any idea how it's done in the API? I know you can retrieve a tweet's parent , but not its children .

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.

Re: A new and improved Twitter API

#64
post #60
post #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. [1] https://nitter.net/

nitter basically gets data from twitter the same way the the web client does it, using the unofficial (and undocumented) APIs

I wonder if anybody tried to document that.

Re: A new and improved Twitter API

#65

I'd love access to the Twitter API for research purposes for my writing, but I'm priced out for that purpose. I can't prove it, but it feels like they only want big businesses researching their markets, and not people like me asking questions about Twitter itself - even though letting people do that would result in negligible additional traffic. This might be controversial and I know people will say that they're a pr…

This is quite new: https://github.com/lschmelzeisen/nasty/

Re: A new and improved Twitter API

#66
post #11

"The number of active real users and followers on Twitter has been greatly exaggerated..." - Inactive Twitter Users. Bots and verified users have ruined the platform.

Personally, I don't have an issue with bots on a platform, as long as they are there to be helpful. In the case of Twitter, I would restrict bots from being able to reply to tweets^, retweet, or like. Only output original things (like automated messaging) or restrict it to DMs. And possibly restrict the use of @s and #s in those tweets so they can't affect trending. That way you can seriously cut down the signal to noise ratio and also make it much easier to spot a bot account.

And please put a BOT label on every bot account and tweet they send. This should be a hard requirement.

^ However, this would interfere with bots like the threading or videothis types. So maybe not apply that restriction.

Re: A new and improved Twitter API

#67
post #60
post #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. [1] https://nitter.net/

nitter basically gets data from twitter the same way the the web client does it, using the unofficial (and undocumented) APIs

Good to know, thanks for mentioning it.

I guess they're quite used to breaking changes in twitter's API, then :) (presuming that a private API must change quite often)

Re: A new and improved Twitter API

#68

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,…

> 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, because there is some absolutely horrible code i will be able to delete as a result of it

Re: A new and improved Twitter API

#69

I'd love access to the Twitter API for research purposes for my writing, but I'm priced out for that purpose. I can't prove it, but it feels like they only want big businesses researching their markets, and not people like me asking questions about Twitter itself - even though letting people do that would result in negligible additional traffic. This might be controversial and I know people will say that they're a pr…

Have you tried contacting Twitter about this? They've given free access to researchers in the past. They'll likely ignore you or say no, and if they say yes it may be more restrictive than you like, but it's worth a shot.

Re: A new and improved Twitter API

#70
post #47

One amazing use of the twitter API is to be able to mass delete your favs, rts, and tweets. It's the only thing I use it for as the API and platform as a whole is otherwise hostile. https://github.com/MikeMcQuaid/TwitterDelete

Last time I checked (2 months ago, I think), the API couldn't fetch more than the 3600 latest liked / posted tweets. Has this changed?

Yes, the API can only get the most recent tweets but the script above can be used with the tweets.csv file provided within your downloadable Twitter Archive. You can delete tweets of any age via the API.

I had to use the archive initially to delete most of the old stuff but now I never have more than a few tweets to delete.

Post reply on HN