From IndieWeb

Bridgy is an open source project and proxy that implements backfeed and POSSE as a service. Bridgy sends webmentions for comments, likes, etc. on Flickr, GitHub, Mastodon, Reddit, and Bluesky, formerly Facebook, Instagram, and Twitter.

It can also POSSE posts, issues, comments/replies, retweets, RSVPs, and likes/favorites/stars to Flickr, GitHub, and Mastodon, formerly Facebook and Twitter.

Finally, it adds webmention support to Blogger, Tumblr,, and Medium blogs.

Screenshot of a blog post with Bridgy backfeed:

How to use

Once you OAuth into, Bridgy polls your silo posts, discovers original post links, and sends comments to those links as webmentions.

It also serves the silo posts, comments, likes, etc. as microformats2 for webmention targets to read.

Example silo-post-as-microformats for reference:

More details.



Bridgy is the fastest way to implement backfeed on your site.

Once you have webmention receiving support implemented on your indieweb site, OAuth into Bridgy and it will send webmentions to your posts for any activity on POSSEd copies of those posts.

Send silo interactions

After you sign up, Bridgy sends all responses to your posts back to your site and other sites that support webmentions. The recipients don't need to be signed up themselves; Bridgy sends webmentions to any server that supports them.

Implementation details

More implementation details here.

Generating h-cards from silo profiles

If your silo profile includes your web site URL, it's included in the h-card that Bridgy generates instead of your silo profile URL, which means that Bridgy comments rendered on original posts will (usually) link directly to your web site. As an example, see the second and third comments here.

This is another step toward making individual web sites the real UX and using silos just as invisible infrastructure (pubsub, friend graphs, etc).

posse-post-discovery on content with no backlinks

As of 2014-04-26, Bridgy uses posse-post-discovery to find original posts, even when the syndicated post does not or cannot include a permalink/citation. (as long as users publish rel-syndication links on their own site).

IndieWeb Examples

Here are some examples of IndieWeb community members using Bridgy along with posts with responses generated by Bridgy:

Aaron Parecki

Aaron Parecki on his notes posts on using p3k since 2013-??-??. E.g.


AnomaLily on E.g.

Barry Frost

Barry Frost on since 2013-??-??. E.g.


Amber Case on since 2013-??-??. E.g.

Christope Duchamp on since 2013-??-??. E.g.

Denton Jacobs

Denton Jacobs

(former user of Bridgy. New site currently doesn't support it.)

Erin Jo Richley

Joschi Kuphal

Matthias Pfefferle

Ryan Barrett

Ben Werdmüller

Felix Schwenzel

(Felix Schwenzel)

Barnaby Walters

gRegor Morrill


Tantek Çelik uses Falcon to automatically POSSE with Bridgy Publish:

  • Since 2015-04-02 likes of Tweets to Twitter - and before that manually since 2014-12-31
  • 2015-05-25 to 2018-04-24 RSVPs to Facebook events - and before that manually since 2014-??-??

Jamie Tanna

  Jamie Tanna uses Bridgy on his site for:

  • Twitter backfeed
  • Twitter publish
  • Meetup publish

Open Source

Bridgy source is maintained on GitHub:



Syndication Links plugin—In addition to providing storage and display for u-syndication links to aid Bridgy for supporting backfeed of comments via Webmention on the social platforms it supports, the Syndication Links plugin also has a meta-box with a simple checkbox interface in the sidebar of the WordPress post editor for publishing content via POSSE. The plugin can be configured for custom syndication endpoints and has the facility to allow it to work with Micropub clients that can search for those endpoints.




Minimize Publish Rerequests

Tantek Çelik tl;dr: minimize:

  • How many times you Webmention Bridgy to ask it to publish a post (should only be once, since updates aren't supported yet.
  • How many "command" links to Bridgy you have on your post (should only need them until you’ve Webmentioned Bridgy Publish and gotten back a syndication URL)

"command links" being links of the form like

General idea: check for an existing syndication link to a destination before attempting to syndicate to it! (Except for update (including salmentions) and delete changes in a post obviously).

Specific method: test for the existence of a syndication link to a particular destination before outputting the command link to Bridgy Publish for that destination. Will reduce requests to Bridgy Publish which don’t actually do anything, both any requests from your own site, and potentially any crawlers that automatically send Webmentions to all links on a page.


if !(.u-syndication[href^=""])
then output Bridgy Publish To Twitter Link


Ryan started working on Bridgy in the summer of 2011, launched the first (WordPress-only) version on 2012-01-08, and relaunched it with webmention support on 2013-12-09.

Previous Features


Google+ support was removed when it shut down in April 2019.


Facebook support was removed in August 2018 due to Facebook API changes...and then resurrected in Feb 2021 with a browser extension.

Publish Facebook Like

From ????-??-?? to 2015-02-14, Bridgy Publish supported POSSEing of like posts of Facebook posts, to "likes" directly on the Facebook posts themselves.

In a round of API changes, Facebook broke the ability to do this, and thus feature was disabled.[1]

This was the first ever regression of Bridgy Publish functionality, due directly to a change by a silo. There is no evidence to suggest this was a deliberately breaking change.[2]

Custom Facebook original-post-discovery

While Facebook was supported, Bridgy could POSSE with custom "See Original" links. Bridgy detected these and correctly sent comments and likes to the linked post.


How can I pay for Bridgy

Q: How can I ever return the favor of Bridgy? Or pay back for it?


Could Bridgy be decentralized

Q: Could Bridgy be decentralized / decentralised / distributed / federated ?

A: Yes, you can for yourself.

  1. Install Bridgy (open source) on your own server. (It runs on App Engine, so you'd probably want to use that, but you could also use a compatible PaaS like AppScale, or a LAMP server with compatibility libraries.)
  2. Configure it with Application API keys for the silos you want to backfeed from.
  3. There is no step three.

There are also other backfeed implementations.

What about links posted by others

Q: Does Bridgy send notifications for links to your site posted by others? E.g.

is effectively a comment on:

And it would be handy to receive it as such.

A: Yes! Details.

How do I recrawl my site

Q: How do I get Bridgy to recrawl my site, like if I’ve updated my h-feed?

A: Click a "retry" / "reload" button in the Responses list.

  1. Go to your Bridgy for a particular silo, e.g.
  2. Click the "retry" / "reload" button next to an item in the "Responses" list in the bottom half of the page

Note: If Bridgy has never found syndication link from your site to that specific silo, it may be more reluctant to recrawl your site.

How do I re-auth

Q: How do I re-auth Bridgy with various silos?


  1. Go to , click the silo you want to re-auth, and approve the prompts.
  2. Once you reach your Bridgy user page, if publish is disabled and you want to enable it, click the silo button next to it.

Can Bridgy re-send a batch of webmentions?

Q: Can Bridgy re-send a batch of webmentions?

A: Yes! Enter the original or silo post URL in the Resend for post box on your user page. Background in

See Also