but now I see it happening again and with a different instance I think there's something wrong
You're viewing a single thread.
21 comments
IIRC, this is how it works by design. Posts don't get federated to another instance unless someone from that instance interacts with it e.g. searches for it, comments on it, etc
Thats only the case for communities, not posts in an already fetched community
What do you mean by "already fetched"? I've been on the fediverse for quite a while and I've never seen new posts from a community be automatically federated across every other instance in the fediverse without someone from those instances interacting with it (e.g. following the community, searching it, etc). Can you point me to where it says it works the way you say? Not saying you're wrong. But would be news to me.
That is what im saying. The thing is with that community above the community has already been interacted with (fetched) in that instance with the op having been making posts in it for a very long time and all previous posts federated. It sounded like you were saying that happens on the post level instead of the community level
Im guessing that this is a bug that got introduced with 0.18.5 since it hasnt been a problem until now
To convert the process into Mastodon terms, a community is like a dummy user, it's not like a hashtag. Making a post to a community is like doing a mention tag to it, like @communityname@instancename, so the community's home instance should always see all the posts to it. (This is the part that I noticed wasn't working)
The community boosts every post to it, so every user who is subscribed/following the community can see the posts that it boosts, which means the instances hosting the subscribers/followers will receive copies of the posts, so federation is automatic there because of the boost.