https://piefed.social/u/rimu posted on Mar 16, 2026 04:04
In reply to: https://activitypub.space/post/1584
In reply to: https://activitypub.space/post/1584
Sounds good to me!
Sounds good to me!
Unless the person replying on Mastodon removes it of course (to save themselves some characters and because they don’t recognise it).
There doesn’t seem any functional difference between your comment (which implicitly Mentions the community), and the original post on thecanadian.social (which explicitly Mentions it). Screenies from activitypub.academy show that replies to both include both Mentions pre-filled.
https://lemmy.world/pictrs/image/a117dab4-1204-4580-9aba-efd22a73b361.png
https://lemmy.world/pictrs/image/03d5dbc1-bd0a-41c0-b37a-639e5e77dbf5.png
https://thecanadian.social/@mike/116234121499688717 didn’t remove the Mention, and so the comment made it to Lemmy. https://mstdn.ca/@cass_m/116234270845317774 did remove the Mention, and so it didn’t.
Specifically for Lemmy btw, the reply at https://mstdn.ca/@cass_m/116234270845317774 demonstrates another problem - that instance requires a signed GET request for its actors, which hasn’t been fully implemented AFAIK.
Good idea, adding this to Lemmy.
Long story short if you’re not on the same instance as the community, Mastodon replies to you won’t make it to the rest of the threadiverse.
Oh… That explains a lot of. Thank you for sharing the cause and the solution (\^_\^)
Did you receive my email from last Thursday? Seems there might be some delivery problem.
I tested this. It works perfectly fine. We can implement this today and remove it when Mastodon supports threadiverse conversations better (I’ll try to make that happen.)
Wow that’s a really proactive response, thank you! Please keep me posted on how it goes
