Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluesky: DM bot user to prompt remote users to enable (opt into) the bridge #966

Open
Tracked by #381
snarfed opened this issue Apr 21, 2024 · 2 comments
Open
Tracked by #381

Comments

@snarfed
Copy link
Owner

snarfed commented Apr 21, 2024

Blocking this on Bluesky OAuth since I want to identify the requesting Bluesky user and include their handle in the prompt DM, but I don't want to make them enter an app password. Bluesky team says OAuth is "a few weeks away," bluesky-social/atproto#2428 (comment), so we can wait.

@snarfed snarfed changed the title Bluesky OAuth flow to send prompt to AP user Support DMs on Bluesky to prompt remote users to enable (opt into) the bridge Jun 23, 2024
@snarfed snarfed changed the title Support DMs on Bluesky to prompt remote users to enable (opt into) the bridge Bluesky: DM bot user to prompt remote users to enable (opt into) the bridge Jun 23, 2024
@snarfed
Copy link
Owner Author

snarfed commented Jun 23, 2024

"A few weeks away" was a bit ambitious on their part. 😆 Also, interestingly, Bluesky shipped DMs before OAuth, so they have parity with the fediverse on that count. Given all that, I'm going to pivot to using DMs for the opt in prompt on Bluesky as well as in the fediverse. Renaming this issue to track that.

@snarfed
Copy link
Owner Author

snarfed commented Jun 23, 2024

In short, the idea here is that Bluesky users should be able to request bridging a fediverse user by DMing their handle to @ap.brid.gy@ap.brid.gy. BF will then DM that user in the fediverse, and they can respond yes or no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant