⁂ Article
More reliably federating microblog responses
I encountered an odd federation issue where microblog responses do not get reliably federated to threadiverse instances.
Example:
- A user on
threadiA instancemakes a new post to a category/community onthreadiB instance. threadiB instancefederates out the post to all followers per FEP 1b12 (so far so good.)- A second user on
microblog instancereplies to that post and tags the user onthreadiA instance(the category/community is omitted — this is how microblogs address content)
I encountered an odd federation issue where microblog responses do not get reliably federated to threadiverse instances.
Example:
- A user on
threadiA.instancemakes a new post to a category/community onthreadiB.instance. threadiB.instancefederates out the post to all followers per FEP 1b12 (so far so good.)- A second user on
microblog.instancereplies to that post and tags the user onthreadiA.instance(the category/community is omitted — this is how microblogs address content)
In this scenario, only the post on threadiA.instance shows the microblog response. threadiB.instance, the party responsible for federating content to followers, is not aware of the new content. Likewise, any followers of threadiB.instance do not receive the content.
How do Piefed and Lemmy handle this scenario? I attempted to address this by having NodeBB federate out Announce(Create(Object)) directly to the group actor, and tested this against crust.piefed.social. Alas, while the activity was accepted, the activity seems to have been ignored.