Comment by saurik

I maintain the position I have had ever since Twitter sold people on the ridiculous idea of "API keys": the correct path has always been adversarial interoperability (as we did back forever ago when people built alternative apps for instant messaging services); if Twitterrific had been designed to use the same API and authority as the official app--maybe as a fallback, if nothing else--Twitter would not have been easily able to kill it... they could try, but it would be a cat and mouse game at best, and the only real recourse they would have would have been to try to detect API abnormalities (which Twitterific could quickly fix, and frankly the skeleton crew at Twitter today likely couldn't do well anyway) to directly punish the end users for continuing to insist on logging in with alternative clients (as Snapchat is forced to do); and, while it is easy to just shut off Twitterific's API key and tell the users "too bad", I think having to take the war to Twitterific's userbase (as the app would be able to keep working forever, with only momentary brownouts) would be a tougher pill for Twitter to swallow, given that it had way too much marketshare at this point.