Not going to lie, Twitter killing off free API access hits me in the feels. I remember with great affection the flood of creativity that happened after we opened up the API, and it's heartbreaking to see that unceremoniously strangled.
I'm relieved that we've got better alternatives, though. While this is perhaps the final straw for many bots on Twitter, it's been a long time coming and the API has long been hobbled compared to the early days. Open protocols or bust. ✊
@bmann I assume they're not going to be charging for *logins*. That'd be really dumb and I would laugh at their incompetence. 😂 Restricting access to eg the post API (or even any API access, eg for reader apps) makes marginally more sense.
My thought here is more: switch the "twitter.com" const to "birdbrainsformastodons.com" and all the old bots (and maybe even client apps) just work again?
@blaine re: logins, since it requires an “app” to be created and API credentials, at this point… 🤷♂️
And yes, totally get your point. With @moaparty we don’t really have a bunch of other people running instances so I would expect the same from this.
An initial API shim instance gets collectively managed. Work to have people host some of their own.
blaine
Boris Mann
bengo