Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A new and improved Twitter API

blog.twitter.com

Post reply on HN
Print view View original

41–50 of 116 posts

Re: A new and improved Twitter API

#41

Post by toyg »

Nav_Panel wrote: post #40
picodguyo wrote: post #21

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

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

Re: A new and improved Twitter API

#42

Post by FroshKiller »

I hope they allow for blocking more than one user at a time at a minimum. Between the rate limit and only blocking one at a time, it takes forever to block a white supremacist and all their scumbag followers via the API. Much faster to just change your country to Germany.

Re: A new and improved Twitter API

#43

Post by numpad0 »

benburleson wrote: post #17
caiobegotti wrote: post #14

These folks from Twitter might suffer from a major disconnection from reality, they burned several bridges of trust over the years and now they just write a small disclaimer about them discovering the hack from this week and the new API apparently does not address issues people had with it in the past (that were used to choke 3rd-party apps). Kudos to the developers working on it directly though, I suppose it takes a…

Exactly. What's their goal with the new API? Will they continue to be hostile to Twitter app developers? Years ago, they made a distinct choice to become a business/celebrity platform, and actively moved away from the utility it could have been. That move cemented my view of Twitter as a dead-end for technology.

Twitter is not as profitable as they want to be, so the corporate wants user to do something monetizable, but users prefer what can’t generate revenue and don’t favor whatever that do, but Twitter is a private company so they have to do it eve if it would only result in its irrelevance, and that will lead to even less profit, then

Re: A new and improved Twitter API

#44

Post by CrazyStat »

benlumen wrote: post #33

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…

I've been collecting Twitter scrapers recently with the idea that I might eventually do something with them. This one [1] seems most promising but I haven't actually tried it.

[1] https://github.com/bpb27/twitter_scraping

Re: A new and improved Twitter API

#45

Post by slightwinder »

sim_card_map wrote: post #6

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

Limits seem to be in the documentation on per resource-base.

https://developer.twitter.com/en/docs/api-reference-index

Or is this the old documentation?

Re: A new and improved Twitter API

#46

Post by kevincox »

picodguyo wrote: post #21

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…

Most importantly none of these items, except maybe threads require a new API. Poll results would just be added to responses, pinned tweets would be a new flag to the search endpoint and a more powerful filtering and search language can just replace the search API. It seems weird that they are tearing it all down and forcing everyone to migrate.

Re: A new and improved Twitter API

#47

Post by esnard »

thinkingemote wrote: post #35

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?

Re: A new and improved Twitter API

#48

Post by Nav_Panel »

toyg wrote: post #41
Nav_Panel wrote: post #40

Earlier quoted context omitted.

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

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

Re: A new and improved Twitter API

#49

Post by wyldfire »

Nav_Panel wrote: post #48
toyg wrote: 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 .

Step 0: build a tree including all tweets,

...

;)

Re: A new and improved Twitter API

#50

Post by ceejayoz »

esnard wrote: post #47
thinkingemote wrote: post #35

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?

If you delete the first 3600 tweets, the next 3600 should now be the latest posted.
Post reply on HN