It can also POSSE posts, comments/replies, retweets, likes/favorites, and event RSVPs to Facebook, Twitter, and Flickr.
Screenshot of a blog post with Bridgy backfeed:
How to use
Once you OAuth into Brid.gy, Bridgy polls your silo posts, discovers original post links, and sends comments to those links as webmentions.
Example silo-post-as-microformats for reference:
Bridgy is the fastest way to implement backfeed on your site.
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.
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).
Custom Facebook original-post-discovery
Facebook supports POSSEing with custom "See Original" links. Bridgy detects these and correctly sends comments and likes to the linked post.
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).
Here are some examples of IndieWeb community members using Bridgy along with posts with responses generated by Bridgy:
Barry Frost on barryfrost.com since 2013-??-??. E.g.
Amber Case on caseorganic.com since 2013-??-??. E.g.
User:Christopheducamp.com on christopheducamp.com since 2013-??-??. E.g.
(former user of Bridgy. New site currently doesn't support it.)
Erin Jo Richley
- Displaying Bridgy webmentions on articles since approximately 2014-05-01
- Using Bridgy Publish notes to POSSE to Twitter since 2014-08-10
- Since 2015-04-02 likes of Tweets to Twitter - and before that manually since 2014-12-31
- Since 2015-05-25 RSVPs to Facebook events - and before that manually since 2014-??-??
Bridgy source is maintained on GitHub:
- On 2016-06-06: 3k users, and more.
- On 2016-07-14: 1000 unit tests.
- On 2015-12-07: 2545 users, and more.
- On 2014-11-06: 1000 users, and more.
- On 2014-03-11, 3 months after its relaunch with webmention support:
- 155 users (72 Twitter, 35 Google+, 34 Facebook, 14 Instagram)
- Seen 56,142 total responses (comments, retweets, likes, RSVPS, etc.)
- Inspected 40k (estimated) pages for webmention endpoints
- Sent 4,576 successful webmentions to 702 different posts on 39 domains
Publish Facebook Like
In a round of API changes, Facebook broke the ability to do this, and thus feature was disabled.
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.
How can I pay for Bridgy
Q: How can I ever return the favor of Bridgy? Or pay back for it?
- file bugs: https://github.com/snarfed/bridgy/issues
- bump bugs you've filed that contributors haven't gotten to
- ideally even tackle fixing a bug yourself and submit a pull request!
- or feel free to donate to the ASPCA or the EFF in the name of "Bridgy".
Could Bridgy be decentralized
Q: Could Bridgy be decentralized / decentralised / distributed / federated ?
A: Yes, you can for yourself.
- 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.)
- Configure it with Application API keys for the silos you want to backfeed from.
- There is no step three.
There are also other backfeed implementations.
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.
- Go to your Bridgy for a particular silo, e.g. https://brid.gy/instagram/tantek
- 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?
- Go to https://brid.gy/ , click the silo you want to re-auth, and approve the prompts.
- 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 https://github.com/snarfed/bridgy/issues/579.