Bluesky is a broad network with lots of worthwhile people and conversations! I hope you’ll give it a chance. Only fully public content is bridged, not followers-only, unlisted, or otherwise private posts or profiles. Still, if you want to opt out, I understand. Feel free to DM me at @snarfed@indieweb.social (different account than this one), email me, file a GitHub issue, or put #nobridge
in your profile bio.
(Admins, if you decide beforehand that you don’t want your instance to federate with Bluesky over the bridge, the domain to limit or block is bsky.brid.gy
.)
A number of us have thought about this for a while now, we’re committed to making it work well for everyone, and we’re very open to feedback. Thanks for listening. Feel free to share broadly.
@snarfed.org @activitypubblueskybridge @fedidevs @fediversenews "Moderate people, not code"
You do not have the resources to moderate everything that will flow over this bridge, so you shouldn't do it. Your project will force this work on other instance mods.
Opt-out is unethical because people aren't aware they're being opted-in, but also because it makes this bigger and dumps more work on other instances.
@snarfed.org @activitypubblueskybridge @fedidevs @fediversenews honestly, we probably need another project like #fedipact to track things like this. I don't want to keep an eye out for every scraper/indexer/bridge project, I just want to pick an instance where my admins defed and opt everyone out. As a bonus, this would place pressure on projects to be opt-in only, so they don't get blocked on sight by whole communities.