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
Samuel
@samuel.fm
I'm guessing bridgy doesn't implement oauth (which I mean, fair enough, it's not a full implementation)
1 8Corey QuinnRight. 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 3Samuelyeah, that's on bridgy to implement oauth. seems like a big undertaking but would be cool!
1 3Corey QuinnLess "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 2Samuelwell 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 5Corey QuinnThat does make some sense. I'm just wondering how to construct an error flow that doesn't send future developers down the same rabbit hole I just climbed out of!
3 4
BorisYou’re (amazingly) bridging a completely different protocol and participating pretty well.
Bridgy as stated is not a fully native account or client.
And bridgy just forwards posts, so no cool non-microblog content like @recipe.exchange or @smokesignal.events or @whtwnd.com
1 3BorisSo yeah, the flow is "use a real AT Protocol account", unfortunately.
(I bet we could convince @snarfed.org to make a full featured PDS www.theverge.com/2024/12/17/2...)
A New Social is a new non-profit that wants to help bridge platforms
The group wants to advocate for users.
theverge.com
RyanBridgy's PDS library github.com/snarfed/arroba already pretty much is a full featured PDS! Minus OAuth. 😎 I ran it as a standalone PDS, separate from Bridgy Fed, early on for testing.
GitHub - snarfed/arroba: Python implementation of Bluesky PDS and AT Protocol, including repo, MST, and sync XRPC methods
Python implementation of Bluesky PDS and AT Protocol, including repo, MST, and sync XRPC methods - snarfed/arroba
github.com
BorisHuh. My bad. It has browseable repos... atproto-browser.vercel.app/at/boris.cos...
But I guess no non-bsky-Lexicons because I can't OAuth or use an app password?
1 1RyanIt is intentional that you can't log in and use bridged accounts directly, via either password or OAuth, fed.brid.gy/docs#use-lik...
...but that doesn't prevent other lexicons! I'm excited to get to those eventually, github.com/snarfed/brid...
support non-Bluesky ATProto apps, eg Whitewind · Issue #1178 · snarfed/bridgy-fed
https://whtwnd.com/ is an early third party ATProto service with its own lexicons (for long form writing) and maybe appview? We should test interop! I tried liking a post, https://snarfed.org/2024-...
github.com
Tom ShermanWhat are you trying to do with oauth on bridgy? 🤔
2 2Corey QuinnMe? Nothing. Someone else tried to use that account to log into a thing I’m building and it exploded.
1
midwest emo fanwas asking this as well - while it would be super cool to log in to your pds account on bridgy i don't think the devs particularly intended for one to do so,
1 1midwest emo fani wonder why one would choose to go this route versus just setting up their own/using bsky.social infra?
Alex Savagetroubleshooting new OAuth implementations is always like being trapped a series of twisty rabbitholes, all alike
2