Post

Jon Buda
@jonbuda.com

Has anyone built a working OAuth flow for Bluesky/atproto in Ruby/Rails, or do I have to hack this together myself? It's definitely more involved that most OAuth implementations, and we'd really rather not just store people's Bluesky passwords, like most apps seem to be doing.

Lucian Ghinda
@lucianghinda.com

I think @marckohlbrugge.com tried this path with Omniauth He shared some gists and code samples here bsky.app/profile/marc...

Marc Köhlbrugge@marckohlbrugge.com

Here's how far I got: github.com/marckohlbrug... It accepts a handle (e.g. marckohlbrugge.com), finds the right auth server to redirect to (looks at TXT records, etc). Redirects you there. Finally redirects you back to the app. That's where I hits an error

github.comGitHub - marckohlbrugge/omniauth-atprotoContribute to marckohlbrugge/omniauth-atproto development by creating an account on GitHub.
Jon Buda
@jonbuda.com

These are fantastic. Working with them now and making progress. Hopefully have feedback/PRs as well. Is it possible to somehow resolve the PDS endpoint that a user should use for authenticated requests? the README references "boletus.us-west.host.bsky.network" but where does that come from?

Frabr
@frabr.lasercats.fr

Thank you ! No currently the gem can't find the pds itself. The boletus pds is one of the bluesky pds (probably where my data is stored), I wrote it in the example to make it clear it was expecting a full pds url (and not an entryway like bsky.social)