4 ms·
A common workaround after Twitter attempted to kill third party client apps was to have users register their own "app" and insert the API keys. So this will put
by Macha 8y ago
A common workaround after Twitter attempted to kill third party client apps was to have users register their own "app" and insert the API keys. So this will put a stop to that.
- pnevares 8y agoI don't think I understand how the rules will affect that, won't the 300 per 3 hours limit on tweets still only affect the "app" a user generated their keys for?
- Macha 8y agoBecause $JOE_AVERAGE_USER is not going to convince Twitter's account approval team that they are a legitimate developer (because they're not).
- notatoad 8y agoThese new limits seem specifically designed to continue allowing that workaround. 300 tweets per three hours is about the upper limit of what a single user would do, so if you're registering a developer account just for personal use you can do that without any manual review or having to demonstrate having a real product. You only require approval from twitter and a product website if you have higher usage than that, which is what would prevent you from using that workaround.
- pnevares 8y agoI think I see what the OP meant, here are relevant excerpts from the article. New API access: > Beginning today, anyone who wants access to Twitter’s APIs should apply for a developer account using the new developer portal at developer.twitter.com. Existing API keyholders: > Eventually, all developers with existing access to our APIs will be required to complete a developer account application in order to maintain their apps.
- notatoad 8y agoMaybe i'm misreading it, but it looks like you're essentially just filling out a form with your contact info and agreeing to the T&C for the initial "application".