You can’t trust corporate APIs. The only ones you can trust are open APIs that aren’t owned by anyone -- like the web, http, html, rss. You have to watch out because the bigco’s will try to own those too. To a large extent Google already owns the web. And they are throwing their weight around in much more consequential ways than twitter. But Google is invisble to the press. That will end someday.
@davew I think we were burnt by Twitter API many years ago. Don’t build a business on top of another business (especially purely based on APIs)

@andychan

okay i've certainly heard that from other people. i expected them to burn us from the beginning. i've been through this with other platform vendors. as they say this isn't my first rodeo.

@andychan Dave has explained many times why he went with #Twitter identities for his services, and also why one can’t wait for perfection, especially with corporate vendors:

http://scripting.com/2017/06/23.html#a100643
http://scripting.com/2019/08/25/150613.html#a152237
http://scripting.com/2021/10/13/140500.html?title=whyWeUseTwitterIdentity#a140548
http://scripting.com/2022/06/08/144243.html?title=whatIsIdentity#a144455

But even though @davew expected to get burned, he couldn’t have foreseen the unprecedented speed, severity, and callousness of their recent actions.

Scripting News: June 23, 2017

It's even worse than it appears.

Scripting News

@mjgardner @andychan

here's the deal, i don't really care. i kind of like the pressure of having to turn this corner quickly. and users won't have anything to complain about if one of the apps is down for a few days during the transition. users have a way of only thinking about themselves and treating individual developers like myself as if we're companies. this way people will feel a bit of appreciation i hope.

@davew @andychan Rule 1b: Don’t break Dave 😄