Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

From UI perspective you are right, but not for APIs.




The APIs definitly used to be open enough that you could hit a "Generate token", hit one endpoint with cURL and then receive a firehose of all public tweets from that moment on, no reviews or validation at all, all you needed was an account + token.

I think this is a huge reason for the initial popularity, because it was trivial to build really fun experiences on top of that, until they cut it off for whatever reason (guessing money, one way or another).

At the same time, you could also view tweets without being logged in, and you saw replies too.


> and then receive a firehose of all public tweets from that moment on

The complete firehose was expensive and paid-only.

You could get a sampling of Tweets at a lower rate through the API. It wasn’t the complete firehose, though.


That sample was complete though as long as there wasn't too many tweets. I.e, as long as your query was specific enough, you _did_ get all tweets.



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: