From fb886ee86abc1c911622a8536974568e9b9d49aa Mon Sep 17 00:00:00 2001
From: Ryan Barrett Bridgy Fed currently supports the web, fediverse, and Bluesky. We're considering adding more networks, including Nostr and Farcaster. Bridgy Fed currently supports the web, fediverse, and Bluesky. We're considering adding more networks, including Nostr and Farcaster. All bridging is fully bidirectional. If you're on a supported network, you can use Bridgy Fed to follow and interact with anyone on any other supported network. Bridgy Fed and Bridgy classic are separate services. They both connect web sites and social networks and translate posts and interactions back and forth, but they each do it very differently.
Bridgy classic, on the other hand, connects IndieWeb web sites to existing accounts on social networks, both centralized and decentralized, and provides backfeed and POSSE (aka cross-posting) as a service.
As an example, here's a visualization of how they each connect web sites to the fediverse:
@@ -796,7 +796,7 @@ I'm Ryan Barrett. I'm just a guy who likes Content moderation for decentralized social networks, and for bridges, is complicated. Bridgy Fed itself doesn't have an exhaustive content moderation policy. Instead, I try to keep these principles in mind:My primary goal is to empower each network's existing moderation ecosystem. Most decentralized social networks have existing, often mature mechanisms for content moderation. The fediverse has blocks and defederation and IFTAS, the IndieWeb has Vouch and Akismet, Bluesky has labeling, even Nostr has mutes and shared mutelists and moderated groups.
+My primary goal is to empower each network's existing moderation ecosystem. Most decentralized social networks have existing, often mature mechanisms for content moderation. The fediverse has blocks and defederation and IFTAS, the IndieWeb has Vouch and Akismet, Bluesky has labeling, even Nostr has mutes and shared mutelists and moderated groups.
I try to ensure that those mechanisms all work with bridged accounts just as well as with native accounts, up to and including defederation. I'm always ready to hear admins' concerns and try to help! But if an instance determines that they need to block a Bridgy Fed network (domain) entirely, that's their prerogative, and I'll support them.
Here are internal details on how Bridgy Fed translates user identity and events between protocols, including some like Nostr and Bluesky/AT Protocol that aren't launched here, or even fully implemented or thought through yet. Caveat hacker!
+Here are internal details on how Bridgy Fed translates user identity and events between protocols, including some like Nostr and Bluesky/AT Protocol that aren't launched here, or even fully implemented or thought through yet. Caveat hacker!
In the tables below, BF is Bridgy Fed. Green parts have been implemented and running here for years, the rest are still in the early design phase.
@@ -1369,7 +1369,7 @@ I'm Ryan Barrett. I'm just a guy who likes Publish outboundh-feed
sync
XRPCs to subscribing BGSessync
XRPCs to subscribing BGSesGot a fediverse account? Follow any 🌐 web site, eg example.com, by searching for @example.com@web.brid.gy in your fediverse instance.
+Got a fediverse account? Bridge it to Bluesky Or follow any 🌐 web site, eg example.com, by searching for @example.com@web.brid.gy in your fediverse instance.
Bridgy Fed currently supports web sites and blogs, the fediverse (via ActivityPub), and Bluesky (via AT Protocol). Nostr and Farcaster are under consideration for the future.
+Bridgy Fed currently supports web sites and blogs, the fediverse (via ActivityPub), and Bluesky (via AT Protocol). Nostr and Farcaster are under consideration for the future.