Thanks for the nitter.net pointer -- I wasn't aware of that. That will be helpful.
I know (in principle) how to use curl to send an authenticated API request via HTTP. That's authenticated; you have to log in. I already have a twitter client for that use case.
There's also unauthenticated API access (read-only public tweets only, as you'd expect). (I assume this is what nitter.net is doing.) Less tracking, but you still have to request an API key, so it is under Twitter's control and they could in theory cut it off. It's still not supporting the basic web principle of "you can GET the flippin' data".
Anyhow, I'm glad this is getting some public attention. I'm a little surprised that I was the first one to make a fuss about it.
I know (in principle) how to use curl to send an authenticated API request via HTTP. That's authenticated; you have to log in. I already have a twitter client for that use case.
There's also unauthenticated API access (read-only public tweets only, as you'd expect). (I assume this is what nitter.net is doing.) Less tracking, but you still have to request an API key, so it is under Twitter's control and they could in theory cut it off. It's still not supporting the basic web principle of "you can GET the flippin' data".
Anyhow, I'm glad this is getting some public attention. I'm a little surprised that I was the first one to make a fuss about it.