feat: add RFC for Bluesky (ATProto) OAuth #63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This builds on our existing OAuth support. There's a bit of additional complexity around giving bsky.storage access to the OAuth sessions created by this new integration, but otherwise ends up looking very similar to our existing GitHub OAuth integration.
alanshaw
approved these changes
Aug 19, 2025
| @@ -0,0 +1,116 @@ | |||
| # RFC: Bluesky OAuth Ligin | |||
Member
There was a problem hiding this comment.
Suggested change
| # RFC: Bluesky OAuth Ligin | |
| # RFC: Bluesky OAuth Login |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview: https://github.com/storacha/RFC/pull/63/files?short_path=9e84d66#diff-9e84d66d4d7f376344e1ee4c098b7a7f37f3f94cc239fa7a1040f1e4458cb15c
This builds on our existing OAuth support. There's a bit of additional complexity around giving bsky.storage access to the OAuth sessions created by this new integration, but otherwise ends up looking very similar to our existing GitHub OAuth integration.
Rough sketch of implementation of some of this here: storacha/w3infra#505