--- For in-house development and/or SaaS software that interfaces with Twitter. Even something like $.10 per 1,000 requests would add up pretty fast for large deployments.
These people could be milked by Twitter. Its a SaaS webapp so they can protect their API access.
3) Charge for "premium membership" that unlocks the api at like $10/user/year
--- app piracy isn't an issue if a user is paying to unlock the API for their account
Also, if app piracy is an issue because they can get ahold of your API keys, that just means you need to route it through your internal API and secure things properly. It isn't Twitters job to fix the fact you don't want to have any infrastructure.
--- For in-house development and/or SaaS software that interfaces with Twitter. Even something like $.10 per 1,000 requests would add up pretty fast for large deployments.
Example? http://freshdesk.com/integrations/help-desk-ticketing-twitte...
These people could be milked by Twitter. Its a SaaS webapp so they can protect their API access.
3) Charge for "premium membership" that unlocks the api at like $10/user/year
--- app piracy isn't an issue if a user is paying to unlock the API for their account
Also, if app piracy is an issue because they can get ahold of your API keys, that just means you need to route it through your internal API and secure things properly. It isn't Twitters job to fix the fact you don't want to have any infrastructure.