Post

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.

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

Oh, excellent! Will dig in

Looks like this is a fully working implementation: bsky.app/profile/frab... (I've been wanting this too, so I'll give it a try soon enough!)

I hope it will serve you well. Don't hesitate to give feedbacks or open issues/PRs, the thing is still quite young, and could be improved in many ways. Oh and there is also a "client" to make authenticated requests once you've got your precious tokens : github.com/lasercatspro...

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)

At first I was a bit confused about where the private data/routes were, and though maybe some private resources were living in specific pds (like bsky threads endpoint), that's why I wanted the user to be able to request any pds. Now I realize it should simply live with the rest of your data.

So, as long as it is clear that any data requested by a user should be in its pds, we could easily implement pds resolution from user handle/did, the didkit gem does it right now github.com/mackuba/didkit