From 0e5be92f08a0b22ff5d9cff2b6df1373947a7846 Mon Sep 17 00:00:00 2001
From: Ryan Barrett From the fediverse To the fediverse From Bluesky To Bluesky From the fediverse To the fediverse About Background Bridgy Fed currently supports the fediverse and the web. We plan to add Bluesky/AT Protocol and Nostr in 2024. 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. Only the people who can already see you and your stuff, as is. Bridgy Fed only bridges fully public data, so if your account is private or protected or followers-only, it won't (can't!) bridge your account at all. Same with DMs and private/followers-only posts; it ignores those. Only the people who can already see you and your stuff, without bridging. Bridgy Fed only bridges fully public data, so if your account is private or protected or followers-only, it won't (can't!) bridge your account at all. Same with DMs and private/followers-only posts; it ignores those. 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.*.brid.gy
domain in my bridged account is ugly. Can I get rid of it and use my own domain/web site instead?
+
+@bsky.brid.gy@bsky.brid.gy
on the fediverse!*.brid.gy
account?
+
+
+
+
+
+
@@ -75,23 +112,7 @@
-
-
-
-
-
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.
+Bridgy Fed - this service - bridges accounts on decentralized social networks like the fediverse, Bluesky/AT Protocol, Nostr, and the IndieWeb directly across those networks. +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:
If you're on the fediverse or Bluesky, and you've opted in but now want to opt out, block the Bridgy Fed bot user for the network you want to opt out of. For example, on the fediverse, block @bsky.brid.gy@bsky.brid.gy
. On Bluesky, block @ap.brid.gy.
Also, if you're on Bluesky and you've hidden your account in the logged out view, Bridgy Fed interprets that as opting out and won't bridge your account.
If you're on the web, feel free to email me, or you can put the text #nobridge
in the profile on your home page and then update your profile on your user page.
*.brid.gy
domain in my bridged account's handle is ugly. Can I get rid of it and use my own domain/web site instead?Yes! All supported networks let you use your own domain as your handle in various ways. This takes a bit of technical setup with DNS and/or a web server, but it's very doable. Here are instructions for web sites bridged into the fediverse.
+To bridge your fediverse account into Bluesky and interact with people there, search for and follow @bsky.brid.gy@bsky.brid.gy
.
If your fediverse account is @[user]@[instance]
, your bridged account will have the handle [user].[instance].ap.brid.gy
in Bluesky. For example, @snarfed@indieweb.social is bridged into Bluesky as @snarfed.indieweb.social.ap.brid.gy.
Bluesky limits profile bios to 256 characters, so if yours is longer in the fediverse, it will be truncated and ellipsized.
+Alternatively, you can find and follow bridged Bluesky accounts without bridging your own account, but they won't see your posts or interactions.
Bridged Bluesky accounts appear in the fediverse as @[handle]@bsky.brid.gy
. For example, @snarfed.bsky.social on Bluesky is bridged into the fediverse as @snarfed.bsky.social@bsky.brid.gy
.
@bsky.brid.gy@bsky.brid.gy
on the fediverse!If you search for @bsky.brid.gy@bsky.brid.gy
on your fediverse instance and you don't see any results, your server may be blocking Bridgy Fed. Check your server's About page to see if bsky.brid.gy
or brid.gy
are in the Moderated serverssection. If they are, you can ask your server admin to reconsider, and include a link to this page for more details.
You can follow any web site, eg example.com, by searching for @example.com@web.brid.gy in your fediverse instance.
+Bridged web sites appear in the fediverse as either @[domain]@[domain]
, @[domain]@web.brid.gy
, or @[domain]@fed.brid.gy
, depending on the fediverse server and whether the web site owner has connected their domain to Bridgy Fed. All bridged web sites behave the same in the fediverse; the different instances in their handles are purely cosmetic.
*.brid.gy
account?In the future, if you haven't opted into the bridge, and someone wants to follow you from a different network, they can request to follow you from the Bridgy Fed home page. The first time this happens, Bridgy Fed will send you a DM to introduce itself and ask if you want to opt into bridging your account. If you reply yes, or follow the Bridgy Fed account that DMed you, your account will be bridged. If you do nothing, or reply no or block the Bridgy Fed account, you won't be bridged.
+Does your fediverse instance support DMs? Only some do. Otherwise, if your instance is blocking Bridgy Fed, you won't receive the DM. Or if it's limiting Bridgy Fed, or you're filtering notifications (this is sometimes on by default!), check the Filtered notifications section of your mention notifications.
+Having said that, if you want to bridge your account, you don't need the DM! Just follow or DM yes to @bsky.brid.gy@bsky.brid.gy
.
Anything that interacts with Bluesky users. This includes replies, @-mentions, likes, reposts, and if you have any Bluesky followers, your own posts. Posts on Bluesky are limited to 300 characters, so longer posts from the fediverse are truncated and ellipsized. Hashtags, links, link previews, images, and even alt text are also included, but not videos since Bluesky itself doesn't support them.
+Lots! Mastodon, Friendica, Misskey, PeerTube, Hubzilla, and more. We're working on interoperation with others; see GitHub issues with the app
label for details.
Mastodon's verified profile links with ✅ green checks are fun! Follow these steps to get one on your Bridgy Fed profile:
+ +rel=me
link on your site that points to https://web.brid.gy/r/https://[DOMAIN]/
for your domain, eg https://web.brid.gy/r/https://snarfed.org/
@snarfed.org@snarfed.org
.When you're logged into a Mastodon instance, searching for your Bridgy Fed user triggers that instance to check and verify its profile link(s) in the background. This only works when you're logged in with a native Mastodon account. Also, each instance does this independently; verified links are not synched across instances.
+Yes! By default, bridged fediverse handles use a subdomain of brid.gy
as their instance, eg @mysite.com@web.brid.gy
, but you can change the instance part to your own domain. It takes a bit of setup and technical know-how, but it's very doable.
First, your domain needs to serve HTTP requests. You don't need an actual web site, but you do need a minimal web server.
+
Second, your web server needs to support SSL. Bridgy Fed uses your domain as your identity, so it depends on SSL to prove that you own it.
+Lastly, your web server needs to redirect a couple URL paths, including query parameters, to the same paths on https://fed.brid.gy/
:
+/.well-known/host-meta +/.well-known/webfinger ++ +
Here are instructions for a few common web servers:
+ +WordPress (self-hosted): install the Safe Redirect Manager plugin, then add these entries:
+
+ /.well-known/host-meta* => https://fed.brid.gy/.well-known/host-meta*
+ /.well-known/webfinger* => https://fed.brid.gy/.well-known/webfinger*
+
+.htaccess
file:RewriteEngine on +RewriteBase / +RewriteRule ^.well-known/(host-meta|webfinger).* https://fed.brid.gy/$0 [redirect=302,last]+(
RewriteEngine on
is optional if you already have it earlier in your .htaccess
. RewriteBase /
is optional if you don't have any other RewriteBase
directives, or if you put this RewriteRule
inside an existing RewriteBase /
section.)
+nginx.conf
file, in the server
section:rewrite ^/\.well-known/(host-meta|webfinger).* https://fed.brid.gy$request_uri? redirect;+
netlify.toml
file.
+ +[[redirects]] + from = "/.well-known/host-meta*" + to = "https://fed.brid.gy/.well-known/host-meta:splat" + status = 302 +[[redirects]] + from = "/.well-known/webfinger*" + to = "https://fed.brid.gy/.well-known/webfinger" + status = 302 ++
To bridge your Bluesky account into the fediverse and interact with people there, follow @ap.brid.gy on Bluesky.
+Your Bluesky account will appear in the fediverse as @[handle]@bsky.brid.gy
. For example, @snarfed.bsky.social on Bluesky is bridged into the fediverse as @snarfed.bsky.social@bsky.brid.gy
.
Alternatively, you can find and follow bridged fediverse accounts without bridging your own account, but they won't see your posts or interactions.
+
Bridged fediverse accounts appear in Bluesky as @[user].[instance].ap.brid.gy
. For example, @snarfed@indieweb.social is bridged into Bluesky as @snarfed.indieweb.social.ap.brid.gy.
Bluesky uses a pull-based event architecture, so we have to poll every bridged user's notifications to discover and bridge interactions, including your initial follow of @ap.brid.gy. We currently do this every 5 minutes. Sorry for the delay! +
Anything that interacts with fediverse users. This includes replies, @-mentions, likes, reposts, and if you have any fediverse followers, your own posts. Hashtags, links, link previews, images, and even alt text are also included.
+ + +Yes! Bluesky's reply controls apply to accounts bridged from the fediverse as well as to native Bluesky accounts..
+Bridgy Fed sends your report to the Bluesky team's official moderation service, which handles it, and takes action if necessary, just like with native Bluesky accounts.
+Also see Bridgy Fed's moderation policy and functionality.
+Another difficulty is that accounts on Bluesky and Nostr have long-lived, server-independent ids. If we used a Bluesky user's PDS domain in their fediverse handle, that handle would change every time they migrated to a new PDS, and they'd lose all of their followers and followings, even though their Bluesky account ID itself hadn't changed.
-To bridge your fediverse account into Bluesky and interact with people there, search for and follow @bsky.brid.gy@bsky.brid.gy
.
Alternatively, you can find and follow bridged Bluesky accounts without bridging your own account, but they won't see your posts or interactions.
-
@[handle]@bsky.brid.gy
, where @[handle]
is their Bluesky handle.
-
-
-You can follow any web site, eg example.com, by searching for @example.com@web.brid.gy in your fediverse instance.
-Bridged web sites appear in the fediverse as either @[domain]@[domain]
, @[domain]@web.brid.gy
, or @[domain]@fed.brid.gy
, depending on the fediverse server and whether the web site owner has connected their domain to Bridgy Fed. All bridged web sites behave the same in the fediverse; the different instances in their handles are purely cosmetic.
Lots! Mastodon, Friendica, Misskey, PeerTube, Hubzilla, and more. We're working on interoperation with others; see GitHub issues with the app
label for details.
Mastodon's verified profile links with ✅ green checks are fun! Follow these steps to get one on your Bridgy Fed profile:
- -rel=me
link on your site that points to https://web.brid.gy/r/https://[DOMAIN]/
for your domain, eg https://web.brid.gy/r/https://snarfed.org/
@snarfed.org@snarfed.org
.When you're logged into a Mastodon instance, searching for your Bridgy Fed user triggers that instance to check and verify its profile link(s) in the background. This only works when you're logged in with a native Mastodon account. Also, each instance does this independently; verified links are not synched across instances.
-Yes! By default, bridged fediverse handles use a subdomain of brid.gy
as their instance, eg @mysite.com@web.brid.gy
, but you can change the instance part to your own domain. It takes a bit of setup and technical know-how, but it's very doable.
First, your domain needs to serve HTTP requests. You don't need an actual web site, but you do need a minimal web server.
-
Second, your web server needs to support SSL. Bridgy Fed uses your domain as your identity, so it depends on SSL to prove that you own it.
-Lastly, your web server needs to redirect a couple URL paths, including query parameters, to the same paths on https://fed.brid.gy/
:
-/.well-known/host-meta -/.well-known/webfinger -- -
Here are instructions for a few common web servers:
- -WordPress (self-hosted): install the Safe Redirect Manager plugin, then add these entries:
-
- /.well-known/host-meta* => https://fed.brid.gy/.well-known/host-meta*
- /.well-known/webfinger* => https://fed.brid.gy/.well-known/webfinger*
-
-.htaccess
file:RewriteEngine on -RewriteBase / -RewriteRule ^.well-known/(host-meta|webfinger).* https://fed.brid.gy/$0 [redirect=302,last]-(
RewriteEngine on
is optional if you already have it earlier in your .htaccess
. RewriteBase /
is optional if you don't have any other RewriteBase
directives, or if you put this RewriteRule
inside an existing RewriteBase /
section.)
-nginx.conf
file, in the server
section:rewrite ^/\.well-known/(host-meta|webfinger).* https://fed.brid.gy$request_uri? redirect;-
netlify.toml
file.
- -[[redirects]] - from = "/.well-known/host-meta*" - to = "https://fed.brid.gy/.well-known/host-meta:splat" - status = 302 -[[redirects]] - from = "/.well-known/webfinger*" - to = "https://fed.brid.gy/.well-known/webfinger" - status = 302 --