Re:Reconstructing Twitter's Firehose
by throwawaymath on Wednesday February 27, 2019 @06:38PM
(#19267912)
I can't imagine these will last long now that they've been posted in a comment on a front page HN story.
[ Parent
| on HN ]
These are hardcoded in the apps. If they disable a key, they would need to release a new version of the app (ok), and all users would need to update (infeasible).
Wouldn't they just enforce the limit with those keys as well?
They explicitly want to cripple third-party apps to push users to use their (awful) official clients, and their way of doing so is to enforce unreasonably low limits.
If they were to do the same with their official clients they'd become unusable.
Sounds like a solid reason to not build around a platform that can arbitrarily kill your project or business. ActivityPub seems to be gaining traction, w/o the beholden to a single entity issue.
A platform that can arbitrarily take down your business like a mobile app on iPhone or Android?
The Twitter for Android key and secret is at least 8 years old