Re:Twitter shut down Emojitracker's access
by Bedon292 on Wednesday March 16, 2016 @03:53PM
(#11300187)
So you are still accessing the streaming endpoint, but you have more keywords than they normally allow? So you are not accessing the entire Firehose and parsing from there, right? Do you regularly update it to include new emoji when they come out? I am thinking about ways to do it on the free stream still, just trying to see where you are already at.
Re:Twitter shut down Emojitracker's access
by williamcotton on Wednesday March 16, 2016 @06:44PM
(#11301262)
You should only expect a level playing field from public infrastructure.
You should never expect a level playing field from private infrastructure.
If anything this is more proof for the need of a public access Twitter-like service using public key crypto for self-signed authentication.
(When Emojitracker originally received elevated access 3 years ago, the project was not famous or well known at all, it was just a slightly more formal version of Me saying: "hey check this out, I think this might be a cool hack but I need access to 900 keywords instead of 400, that ok?" and Twitter: "yeah cool, no problem dude.")