I think we are talking past each other. I am not talking about the Account Activity API or Site Streams. I am talking about their FREE streaming API that let's you stream millions of tweets per day. I am just trying to raise awareness about how easily people can pull user data en masse from Twitter, which is very relevant to the article. It's public, but people still don't realize just how easy it is to do.
> I am talking about their FREE streaming API that let's you stream millions of tweets per day. I am just trying to raise awareness about how easily people can pull user data en masse from Twitter, which is very relevant to the article. It's public, but people still don't realize just how easy it is to do.
Yes, that's an endpoint off stream.twitter.com. It's not only limited in terms of how much relevant info you'll be able to access (in the context of the original post), but also heavily rate-limited for clients.
I agree that it's confusing that Twitter has so many different components of their API which use overlapping names, but I've looked into this extensively because, as I mentioned at the outset, I wrote the client libraries for these and still maintain them.
Again, this is the API I am talking about: https://developer.twitter.com/en/docs/tweets/filter-realtime...