POSSE put my posts on Bluesky. The next question was what happens when someone likes or replies to the Bluesky copy. Without a backfeed, those reactions stay on Bluesky and never reach the original post. Bridgy closes that loop.
What Bridgy does
Bridgy is a hosted service. It polls social networks for reactions to posts that link back to your site. When it finds a like, repost or reply, it sends a webmention to your endpoint on your behalf. On my old site, webmention.io received and stored it and made it available through its API (Receiving and sending webmentions).
From end to end:
- An article is published at
adrian-altner.de/articles/.... - A Bluesky post is created with the article URL as the embed link.
- Someone likes the Bluesky post.
- Bridgy polls Bluesky, finds the like and sends a webmention to
webmention.io/adrian-altner.de/webmention. - On the next deploy the
WebMentionscomponent fetches from webmention.io, and the like appears under the article.
Setup
Connecting a service to your own identity usually means yet another account. Bridgy logs you in by domain, through the same IndieLogin flow as webmention.io. After that, connecting Bluesky took one click. Bridgy reads the Bluesky profile, finds posts that link to the domain and starts polling.
The default poll interval is 30 minutes. A "Crawl now" button starts a scan at once, which helped while I tested the first reactions.1
What comes back
Bridgy sends webmentions for three kinds of reaction:
- likes, as
like-of; - reposts, as
repost-of; - replies, as
in-reply-to.
My WebMentions component already handled all three in separate sections. Likes and reposts showed as rows of avatars, replies as comments with author name and text.
Deletions come back too
When a like or reply is deleted on Bluesky, Bridgy notices on the next poll and sends an updated webmention, and webmention.io removes the entry. The next deploy showed the change, and the avatar disappeared from the row of likes. Without this, deleted reactions would have stayed on the original post for good.
Notes work the same way
Notes went to Bluesky with the same embed structure as articles: the note URL as uri, the description as post text. Bridgy picked up reactions on them the same way, and they came back as webmentions to the original note URL.
The full loop
Write on your site
→ deploy syndicates to Bluesky (AT Protocol)
→ Bluesky followers interact
→ Bridgy backfeeds interactions as webmentions
→ webmention.io stores them
→ next deploy renders them on the original post
The canonical URL stayed mine, and the reactions found their way back to it wherever they happened.
Takeaways
- POSSE without backfeed is half the loop. Otherwise the copy collects all the reactions and the original stays silent.
- Bridgy needs no infrastructure. A hosted service polling every 30 minutes was cheaper than my own AT Protocol scraper, and it used the IndieLogin I already had.
- The embedded link is the anchor. As long as the Bluesky post carries the original URL, Bridgy can match the reactions to it.
- Topic
-
- IndieWeb Publishing on your own domain first and connecting personal websites with open standards such as Webmention and Microformats.
- Basis for
-
- Troubleshooting Mastodon Backfeed A runbook for Mastodon, Bridgy and webmention.io: token scopes, deploy order, trailing slashes, 429s on media uploads and reactions that are gone upstream.
- Builds on
-
- POSSE to Bluesky with the AT Protocol A Node script at the end of every deploy that posts new articles from the RSS feed to Bluesky as rich link cards, straight through the AT Protocol API.
- Receiving and Sending Webmentions Incoming webmentions through webmention.io, rendered at build time in Astro, and outgoing ones sent by webmention.app after every deploy.
- Mentioned in
-
- Marking Up Posts with Microformats2 h-entry h-entry, h-card, h-feed and u-syndication classes on articles, notes and photos of an Astro site, machine-readable without any visible change.
- Tags