Since you asked...
github.com/snarfed/brid...
OAuth endpoints missing from atproto.brid.gy · Issue #1901 · snarfed/bridgy
According to the AT Protocol OAuth spec, every PDS (Personal Data Server) must implement OAuth endpoints at /.well-known/oauth-protected-resource. However, atproto.brid.gy currently does not implem...
github.com
Right. The bug is that a bridgy BlueSky account (like, say @cowperthwait.sfba.social.ap.brid.gy) can't authenticate via OAuth flows to BlueSky until they change their current implementation a smidgen.
They can implement it or not, but breaking OAuth seems bad.
1 3Less "implement" and more "not break other clients."
1. I set up a Bsky account using bridgy.
2. I use that account normally. Now I try to use that account with Client Foo, a bsky client that uses OAuth instead of app passwords.
3. That account will fail to authenticate for Client Foo.
1 2Samuel
@samuel.fm
well if bridgy is your PDS, you need your PDS to implement oauth to do oauth. bridgy is an incomplete PDS implementation. obviously it is good to have and yes I agree it would be nice if bridgy had it
you can always migrate your account to a PDS running our PDS software if you need oauth
1 5