Bridgy Fed lets you interact with federated social networks like <ahref="https://joinmastodon.org/">Mastodon</a> and <ahref="https://project.hubzilla.org/">Hubzilla</a> from your <ahref="https://indieweb.org/">IndieWeb</a> site. It translates replies, likes, and reposts from <ahref="http://www.webmention.org/">webmentions</a> to federated social networking protocols like <ahref="https://activitypub.rocks/">ActivityPub</a> and <ahref="https://en.wikipedia.org/wiki/OStatus">OStatus</a>, and vice versa.
This isn't <ahref="https://indieweb.org/syndication">syndication</a> or <ahref="https://indieweb.org/POSSE">POSSE</a>! You don't need an account on Mastodon, Hubzilla, or anywhere else. Bridgy Fed lets your site act like a first class member of the <ahref="https://en.wikipedia.org/wiki/Fediverse">fediverse</a>. People on federated social networks (aka fedsocnets) will see your posts directly from your own site, and vice versa.
Here's <ahref="https://mastodon.technology/@snarfed/3194674">an example on Mastodon</a>, and <ahref="https://hubzilla.com.br/channel/snarfed/?f=&mid=459a0b809f2d5395efd5d581dad70043c5ea9e1dbd156bc5e1b2f771c98eb970@hubzilla.com.br&zid=snarfed%40hubzilla.com.br">another example on Hubzilla</a>.
The instance must be running at least <ahref="https://hackernoon.com/mastodon-and-the-w3c-f75f376f422">Mastodon 1.6</a>, and more reliably with 2.0 and up. You can find its version on the bottom or right of its <code>/about/more</code> page, e.g. <ahref="https://mastodon.social/about/more">mastodon.social/about/more</a>.
The instance must be running <ahref="https://hub.somaton.com/channel/mario/?f=&mid=6db16e0e253c3c376cb921e7b31f94c24522933d7e54c6cf9febaa05359ab2fe@hub.somaton.com">Hubzilla 2.6</a> or higher. You can find its version on its <code>/siteinfo</code> page, e.g. <ahref="https://hub.somaton.com/siteinfo">hub.somaton.com/siteinfo</a>. It also needs the GNU Social addon installed and enabled, and you also need to enable it in your account settings on the <em>Feature/Addon settings</em> page (<code>/settings/featured</code>).
We're aware of the sites below, and we've made progress on some, but they're not yet supported. Click through and vote for their feature requests if you're interested in any of them!
</p>
<ul>
<li><em><ahref="https://github.com/snarfed/bridgy-fed/issues/7">Diaspora</a></em>, via OStatus.</li>
<li><em><ahref="https://github.com/snarfed/bridgy-fed/issues/9">Friendica</a></em>, via OStatus.</li>
<li><em><ahref="https://github.com/snarfed/bridgy-fed/issues/8">GNU Social</a></em> (née StatusNet), via OStatus.</li>
<li><em><ahref="https://github.com/snarfed/bridgy-fed/issues/11">MediaGoblin</a></em>, via ActivityPub?</li>
<li><em><ahref="https://github.com/snarfed/bridgy-fed/issues/12">Pleroma</a></em>, via OStatus.</li>
<li><em><ahref="https://github.com/snarfed/bridgy-fed/issues/10">postActiv</a></em>, via ActivityPub or OStatus.</li>
<liid="setup"class="question">How do I set it up?</li>
<liclass="answer">
<p>
First, your site needs to support <ahref="http://www.webmention.org/">webmentions</a>. <ahref="https://indieweb.org/webmention#Publishing_Software">Check out the IndieWeb wiki</a> for instructions for your web server.
Next, add an <ahref="https://en.wikipedia.org/wiki/Atom_(standard)">Atom</a> feed if your site doesn't already have one. If you're on <ahref="https://wordpress.org/">WordPress</a>, install the <ahref="https://wordpress.org/plugins/atom-default-feed/">Atom Default Feed plugin</a>.
<!-- or just <a href="https://codex.wordpress.org/WordPress_Feeds#Finding_Your_Feed_URL">add this</a> to your HTML header:<br /> -->
Otherwise, you can use <ahref="https://granary-demo.appspot.com/">granary</a>. Just add this to your site's HTML <code><head></code> and fill in <code>DOMAIN</code> with your site's domain:
If you want people on fedsocnets to see your posts, your site will also need to support <ahref="https://indieweb.org/WebSub">WebSub</a> (née PubSubHubbub). <ahref="https://github.com/tootsuite/mastodon/issues/1441#issuecomment-302969948">Example details for Mastodon.</a> If you're on a CMS, it may already have a plugin! <ahref="https://wordpress.org/">WordPress</a> has <ahref="https://indieweb.org/WebSub#WordPress_Plugins_for_PuSH">a couple</a>, and <ahref="http://withknown.com/">Known</a> has it <ahref="https://indieweb.org/WebSub#1000s_of_Known_Sites">built in</a>. Or you can use <ahref="https://superfeedr.com/publisher">Superfeedr</a> or <ahref="https://switchboard.p3k.io/">Switchboard</a>.
Finally, configure your web site to redirect these URL paths to the same paths on <code>https://fed.brid.gy/</code>, including query parameters:
</p>
<pre>
/.well-known/host-meta
/.well-known/host-meta.xrd
/.well-known/host-meta.jrd
/.well-known/webfinger
</pre>
<p>Here are instructions for a few common web servers:</p>
<ul>
<li>
<p><em><ahref="http://wordpress.org/">WordPress</a> (self-hosted)</em>: install the <ahref="https://wordpress.org/plugins/safe-redirect-manager/">Safe Redirect Manager</a> plugin, then add these entries:</p>
Federated social network identities take the form <code>@username@example.com</code>, like an email address with a leading <code>@</code>. Your site's identity via Bridgy Fed will be <code>@me@yourdomain.com</code>. Once you've <ahref="#setup">set up Atom and WebSub on your site</a>, people can follow you at that address.
Most fedsocnets also publish Atom themselves, so you can add profile URLs like <ahref="https://mastodon.technology/@snarfed">mastodon.technology/@snarfed</a> to your <ahref="https://indieweb.org/reader">reader</a> and see their posts there too.
To like, repost or reply to a post on a fedsocnet, create an <ahref="https://indieweb.org/like">indie like</a>, <ahref="https://indieweb.org/repost">repost</a>, or <ahref="https://indieweb.org/reply">reply</a> as usual, and include a link to <code><ahref="https://fed.brid.gy/">https://fed.brid.gy/</a></code> in that post. Your web server should then <ahref="#setup">send Bridgy Fed a webmention</a>, which it will translate to a Salmon slap or ActivityPub activity and forward to the destination. For example:
<p class="<spanclass='keyword'>e-content</span>"><spanclass='value'>Highly entertaining. Please subscribe me to your newsletter.</span></p>
To receive likes, reposts, and replies from fedsocnets, just make sure your site accepts webmentions! Bridgy translates incoming Salmon slaps and ActivityPub activities to webmentions and sends them to your site.</p>
For replies, the source will usually be the permalink on the social network itself. For likes and reposts, the source will usually be a proxy page on <code>fed.brid.gy</code>. For best results, <ahref="https://brid.gy/about#appspot">make sure your webmention handler detects and handles <code>u-url</code> links</a>!
<liid="cost"class="question">How much does it cost?</li>
<liclass="answer">
<p>Nothing! Bridgy Fed is small, and it doesn't cost much to run. We don't need donations, promise.
</p>
<p>If you <em>really</em> want to contribute, <ahref="https://github.com/snarfed/bridgy-fed/issues">file an issue</a> or <ahref="https://github.com/snarfed/bridgy-fed">send a pull request</a>, or <ahref="https://opencollective.com/indieweb">donate to the IndieWeb</a>!
</p></li>
<liid="who"class="question">Who are you? Why did you make this?</li>
<liclass="answer">
<p>
I'm <aclass="h-card"href="https://snarfed.org/">Ryan Barrett</a>. I'm just a guy who
<ahref="https://snarfed.org/2012-07-25_why_i_have_my_own_web_site">likes the web</a> and likes <ahref="https://indieweb.org/why">owning my data</a>.
</p>
</li>
<liid="privacy"class="question">What do you do with my data?</li>
<p>Nothing! Bridgy Fed isn't a business, and never will be, so we don't have the same motivations to abuse your data that other services might. More concretely, Bridgy Fed won't ever send you email, it stores as little of your <ahref="http://en.wikipedia.org/wiki/Personally_identifiable_information">PII</a> (personally identifiable information) as possible, and it <em>never</em> has access to any of your passwords.
<p>I started thinking about bridging federated social networks and peer to peer networks when I discovered them in the early 2000s. I started talking about bridging them to the IndieWeb in 2016, <ahref="http://indieweb.org/2017/ostatusbridge">led a session on it at IndieWeb Summit</a> in July 2017, wrote up <ahref="https://snarfed.org/indieweb-activitypub-bridge">concrete</a><ahref="https://snarfed.org/indieweb-ostatus-bridge"> designs</a> soon after, and started working on Bridgy Fed in August 2017.