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.
Reviewed by adrian
on
Automating the syndication to Mastodon was the easy part. Getting likes, reposts and replies from Mastodon onto the canonical post, and off it again when they were deleted, took much more care. This is the checklist that came out of debugging real failures on my old site.
The setup
- Canonical site: a static Astro 6 build at
adrian-altner.de. - Bridge: Bridgy, which maps Mastodon reactions to canonical URLs through
u-syndication. - Store: webmention.io, queried at build time and from the browser for live updates.
"Outside the authorized scopes"
Mastodon returned:
{"error":"This action is outside the authorized scopes"}
The access token lacked permissions. A token for script-based posting needs at least:
write:statuseswrite:media
It also helps to drop API calls that need further scopes. Removing a verify_credentials check before posting got rid of a whole class of scope errors that had nothing to do with posting.
No backfeed on Bridgy
A common trap: someone reacts to the Mastodon copy before the site has been redeployed with the matching u-syndication link (Syndication links from state). If Bridgy cannot map the reaction to a canonical page, it shows nothing. The order matters:
- Deploy first, so "Shared on Mastodon" is live on the page.
- Use Bridgy's
Poll noworCrawl now. - If it is still missing, use
Resend for post. - Retry the reaction.
The u-syndication link has to be on the canonical page when Bridgy crawls. Any other order loses data silently: the reactions happened, but Bridgy had nowhere to send them.
Trailing slashes
webmention.io matches targets exactly. .../hello-world and .../hello-world/ are two different targets. When debugging, always query the canonical URL exactly as it appears on the page, slash included. Otherwise an empty result sends you after the wrong bug for an hour.
429 on media uploads
Large backfills hit the media API limits fast. The syndication script now retried media uploads with backoff and honoured Retry-After when the server sent it. The status went out even if a media upload failed in the end, so images did not block the backfill.
Deleted likes and reposts still showing
The most annoying failure. Deletions do not always pass cleanly through every layer: webmention.io can still hold the old reaction, and the source URL can still return HTTP 200 when the reaction itself is gone. The fix was to check each reaction upstream, not only whether its URL exists:
- Mastodon: check
favorited-byandreblogged-byagainst the status's interaction APIs. - Bluesky: check
liked_byandreposted_byagainst the public API lists. - Replies: check directly through the platform APIs that the source post still exists.
If the reaction or the source post is gone upstream, it is filtered out at render time, with no manual work in the dashboard.
The browser refresh kept stale reactions
Even with correct filtering on the server, the page stayed stale when the browser refresh only handled additions. The webmentions component now tracked the current count and re-rendered in both directions, when mentions were added and when they were removed. Deletions became visible without pruning them by hand in the webmention.io dashboard.
A debugging order
When something looks wrong:
- Check the canonical target URL, including the trailing slash.
- Look at the filtered output of the local endpoint.
- Check upstream that the reaction or post still exists.
- Start a Bridgy poll or crawl.
- Only then delete anything by hand in the dashboard.
Most "it still shows" problems were one of these five, not a rendering bug.
Takeaways
- Check token scopes first.
write:statusesandwrite:mediaare the minimum; cut any calls that need more. - Deploy before reacting. Bridgy needs the
u-syndicationlink on the page at crawl time. - A trailing slash is part of the identifier, in webmention.io, in state files and in component queries.
- Re-validate the reaction, not just the URL. A source URL can return 200 long after the like is gone.
Based on
-
Troubleshooting Mastodon Backfeed and Stale Webmentions
(
raw/2026/2026-03-24/troubleshooting-mastodon-backfeed-and-stale-webmentions.md) [post]
Topic
- IndieWeb Publishing on your own domain first and connecting personal websites with open standards such as Webmention and Microformats.
Builds on
- Bluesky Reactions as Webmentions with Bridgy Bridgy polls Bluesky for likes, reposts and replies to syndicated posts and sends them back as webmentions, so they appear on the original post.
- Live Webmentions on a Static Site Webmentions rendered at build time plus a silent client-side refresh, so new likes and replies show up on a static Astro site without SSR or a redeploy.
- POSSE to Mastodon A Mastodon syndication script for articles and notes: state keyed by canonical URL, OG image uploads that fail open, backoff on 429, dry runs and batch limits.
Mentioned
- Syndication Links from State Astro imports the syndication state file at build time and renders u-syndication links on every post, so the frontmatter never needs a second edit.