bridgy icon indicating copy to clipboard operation
bridgy copied to clipboard

Replies of replies don't seem to be bridged from Mastodon

Open eerii opened this issue 1 month ago • 2 comments

I have this Mastodon post: https://todon.eu/@koala/115622368172883843

The top level public replies have sent a Webmention, as did my own reply to a reply.

However, anything that is a reply to a reply (thread) doesn't seem to be bridged, even if I tried the workaround of placing it in the discover box mentioned in one of the other issues. Take this https://todon.eu/@[email protected]/115623682256366848

This is the log. It created the bridgy page for the comment.

However, it received a 201 from webmentions.io with a no_link_found status:

{
  "status": "no_link_found",
  "source": "https://brid.gy/comment/mastodon/@[email protected]/115623682256366848/115623682256366848",
  "target": "https://conflor.es/blog/2025-11-27-interop-and-mathml/",
  "summary": "The Microformats at the source URL do not contain a link to the target URL. Check the source URL in a Microformats parser such as php.microformats.io"
}

Inspecting the url with php.microformats.io gives this. The in-reply-to is set to the post it is replying, and there is no mention of the original post, so I'm guessing that's why microformats.io doesn't find a link.

I'm not sure this is even supported, so feel free to close this if it is out of scope, but I was just curious.

eerii avatar Nov 28 '25 12:11 eerii

Oof, sorry for the trouble, and thanks for reporting! Mastodon replies-to-replies are indeed best effort only, they're complicated for a number of reasons, but I can look at this. At minimum, we shouldn't send invalid webmentions like this.

snarfed avatar Nov 29 '25 21:11 snarfed

That makes a lot of sense, I can see how they are quite complicated. I was just curious about it :) Thank you!

eerii avatar Dec 04 '25 12:12 eerii