Replies: 1 comment
-
|
Hi @molind, thanks for reaching out, and for the detailed writeup! This has indeed been discussed before, primarily in #1535 . The discussion there probably has answers to most or all of your questions. There's also some related discussion in #1471 . You'll probably also be interested in #2042 . Stay tuned for more news there soon! cc @anujahooja |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The Problem
Currently, when an unbridged Bluesky user replies to a bridged Mastodon user's post, the Mastodon user receives a DM notification digest (thanks for the recent unbridged notifications feature! 🎉). However, they can't easily continue the conversation — they'd need to go to Bluesky to reply, or hope the Bluesky user opts into the bridge.
This creates friction for cross-network conversations. The Bluesky user already engaged with bridged content, clearly intending to communicate, but the conversation hits a dead end.
Proposed Solution
Treat replying to a bridged post as implicit consent for that specific reply to be bridged back.
When an unbridged Bluesky user replies to a bridged Mastodon post:
This would be conversation-scoped, not account-scoped — we're not bridging their entire account, just their voluntary participation in a specific thread they chose to join.
Why This Makes Sense
Expectation alignment — When someone replies to a post clearly marked as bridged from Mastodon, they reasonably expect the original author to see and respond to their reply
Analogous to email — If I email someone, I expect they might reply. Replying is participation.
Already public content — The reply is already public on Bluesky. We're just delivering it to the person it was addressed to.
Reduces friction — Currently, meaningful cross-network conversations require both parties to understand and opt into bridging. This is a high bar for casual interactions.
Possible Implementation
For replies from unbridged users to bridged posts:
@handle@bsky.brid.gyformat)NotewithinReplyToAddressing Consent Concerns
I understand Bridgy Fed chose opt-in for good reasons after community feedback. This proposal is different:
Potential safeguards:
#nobridgein bioQuestions for Discussion
Beta Was this translation helpful? Give feedback.
All reactions