Skip to content

Stop WhoToFollow from recommending muted or blocked accounts - #37

Closed
Pitchfork-and-Torch wants to merge 19 commits into
mainfrom
cursor/wtf-mute-block-exclude-a2f3
Closed

Stop WhoToFollow from recommending muted or blocked accounts#37
Pitchfork-and-Torch wants to merge 19 commits into
mainfrom
cursor/wtf-mute-block-exclude-a2f3

Conversation

@Pitchfork-and-Torch

Copy link
Copy Markdown
Owner

Bug

WhoToFollow excluded_user_ids only sent previously shown WTF accounts. It never sent muted or blocked user ids.

For You and Latest Following blender pipelines never loaded those SGS lists. Phoenix loads them for post filters only. WTF runs at the blender layer, so VF never sees the recommended accounts.

SGS get_muted_user_ids / get_blocked_user_ids Err is ignored by query hydration (update is skipped). Empty lists look like "muted nobody".

This is not xai-org#137 (VF primary-author relationship Failed). This is not #23 / xai-org#140 (quoted-author mute on posts). ListTimeline / ListLatest are not in this dump.

Five-line proof

  • Entry: MutedUserIdsQueryHydrator / BlockedUserIdsQueryHydrator (SGS list membership). For You / Latest Following blender queries never ran them.
  • Sink: WhoToFollowSource::get_excluded_user_ids → ARM WhoToFollowReactiveContext.excluded_user_ids
  • Break: exclude set was fatigue-only; list Err left empty vectors; blender never hydrated the lists
  • Viewer effect: a muted or blocked account can appear in Who To Follow on For You and Latest Following
  • Twin: FollowingRepliedUsersHydrator already excludes muted+blocked ids; AuthorSocialgraphFilter already uses the same lists for posts

Change

  • Mark mute/block lists hydrated only after a successful SGS read. Err leaves the flags false.
  • Load both lists on the For You and Latest Following blender pipelines.
  • WhoToFollow stays off until both lists are ready. excluded_user_ids puts muted/blocked ids first, then fatigue ids.

Genuine empty lists (viewer muted/blocked nobody) still enable the module.

Tests

  • Enable is false until both list flags are set
  • Muted and blocked ids are excluded before fatigue ids
  • A full mute/block cap does not admit a fatigue id
  • Hydrator update sets the ready flag

Standalone decision-table harness (same exclude / ready arms): 8/8 passed.

cargo test cannot run. Public dump has no Home Mixer manifest.

Leftover

Mixer AuthorSocialgraphFilter still treats an unready empty list as nobody muted/blocked for quoted/RT authors. After xai-org#137, VF is the sink for primary-author mute/block. WTF has no VF sink.

Fork PR: none

Open in Web Open in Cursor 

CI agent and others added 19 commits August 14, 2026 20:55
in_network_ids is passed to the VF client without deduplication, while
oon_ids is deduped four lines below. retweeted_tweet_id is pushed for
every candidate that has one, so the same ID repeats once per retweet of
a given post — most often when that post is going viral.

Neither VfClient implementation dedupes its input: StratoVfClient builds
one call per element, and XaiVfClient chunks by XAI_VF_MAX_BATCH_SIZE, so
duplicates consume batch slots and can force an extra round trip.

Not a correctness issue — results collapse into a HashMap keyed by tweet
ID — but redundant work on the For You serving path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deduplicate in_network_ids before VF lookup
SGS mute/block list hydrators now mark the query ready only on a
successful read. For You and Latest Following blender pipelines load
those lists. WhoToFollow stays disabled until both lists are ready and
sends muted/blocked ids in excluded_user_ids ahead of fatigue ids.

Co-authored-by: Jon Bailey <Pitchfork-and-Torch@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants