Goodbye, Twitter third-party login
So, a little while ago I did an extremely unscientific poll on login methods via Authl on this website. The results of that (measured by folks who accessed my site for any authenticated reason, not just folks visiting the login method poll):
- 8 signed in via Fediverse (Mastodon/Pleroma/etc.)
- 4 signed in via IndieAuth
- 7 signed in via email
Not a single one signed in via Twitter.
So anyway, today Twitter rolled out the API payments change. They had claimed that third-party OAuth would continue to be a free feature, but they still banned my old API keys (with a supposed “terms of service violation”) and required me to create a new application under the new payments-enabled regime.
Even with nobody logging on via Twitter, I figured I’d make a token effort to keep Twitter signin working. I created a new app on the free tier, set up its API token and endpoints, redeployed my Authl config with the new settings, and…
It didn’t work, and the Twitter developer console gave me no useful information about how to fix it.
So, Twitter login is disabled and I don’t have any plans to bring it back. If there’s a code change necessary in Authl, someone else is more than free to make an appropriate pull request and a documentation fix, but at this time I have no interest in fixing it myself.
As always my top recommendation for third-party login is using IndieAuth (just because having control over your own web presence is always a good thing), but Fediverse is also a pretty good approach. I don’t super recommend email for a couple of reasons but it’s at least already available to pretty much everyone on the Internet. But those are the three primary mechanisms I’d suggest for people building web apps (and if they’re building those apps in Python, definitely consider Authl for that purpose).
Before commenting, please read the comment policy.
Avatars provided via Libravatar