Her post included links to other posts, like this one which is a mb-powered site. Tracy's site sent Webmentions, so the mb webmention endpoint received that. It appears mb incorrectly interpreted it as a direct reply (instead of a mention). In the conversation view, mb shows: @petebrown: followed by the contents of her article, sans the title.
This gave the appearance of Tracy replying to Pete's conversation with a lengthy post, which it wasn't.
After this happened, she removed the in-reply-to and changed it to a quotation post in attempt to remove it from the mb conversation view.
What I would expect to happen:
Either skip webmentions where the mb URL is not in the in-reply-to, or show it as a short [name] mentioned this [link].
This one is kind of odd, will do my best to describe what I think happened:
Describe the problem:
Tracy's article originally had microformats2
in-reply-tothis Substack article.Her post included links to other posts, like this one which is a mb-powered site. Tracy's site sent Webmentions, so the mb webmention endpoint received that. It appears mb incorrectly interpreted it as a direct reply (instead of a mention). In the conversation view, mb shows:
@petebrown:followed by the contents of her article, sans the title.This gave the appearance of Tracy replying to Pete's conversation with a lengthy post, which it wasn't.
After this happened, she removed the
in-reply-toand changed it to a quotation post in attempt to remove it from the mb conversation view.What I would expect to happen:
Either skip webmentions where the mb URL is not in the
in-reply-to, or show it as a short[name] mentioned this [link].