sourcehut offers OAuth 2.0 authorization process via meta.sr.ht. And now that sourcehut implements OAuth tokens auto-renewal mechanism, you don't have to issue tokens manually every year.
It would be great if senpai supports OAuth client authorization so that people who use chat.sr.ht as a irc bouncer don't need to care about token expiration in the future.
Blocked on sourcehut implementing dynamic client registration https://www.rfc-editor.org/rfc/rfc7591.html and advertising the endpoint in its .well-known/oauth-authorization-server.
Also blocked on https://chat.sr.ht/.well-known/oauth-authorization-server 404 (but https://meta.sr.ht/.well-known/oauth-authorization-server works).