@Fidgetcetera It is very simple. Let me help to explain. A toot must ether:
—
A). Be from someone on your instance,
—
B). Be from someone who your instance is monitoring, because someone on your instance follows them,
—
or C). be boosted by someone that your instance is monitoring.
—
Those are the only ways. Sometimes, toots have inaccurate information, because of the nature of the distributed system. It can look like they where not boosted.
@NthTensor Okay, so let's take this example. https://mstdn.jp/users/hatenapluse/updates/545433 showed up in my federated timeline. It has no boosts according to either the web client here on simstim.club OR mstdn.jp's page. Scrolling through their followers, no one on simstim.club follows them.
This happens very regularly, to the point where my only guess is someone is boosting and unboosting toots en masse?
@Fidgetcetera The web client is, unfortunately, not accurate. Any given instance can only track the boost /on that given instance/.
—
Boosts on other instances do not require communication with the server of origin, and so are very hard to track.
—
By design, it is almost impossible to track, from the server of origin, where and how toots propagate to.
—
The server or origin is only in charge of the initial dispatch.
—
Assume there was boosting somewhere.
@NthTensor Nevermind, I figured it out thanks to this post. https://mastodon.art/users/Curator/updates/112
There was one user being followed by one person who was mass auto-replying to users, thus causing the original post to federate.
@NthTensor Thanks for being entirely wrong and overexplaining concepts I completely got, though.
@NthTensor @Fidgetcetera Even simpler terms: it's all toots that have reached your instance.
There are more cases than just those, but they are the most common ones.