Stop RankingScorer author diversity from keying the retweeter - #54
Closed
Pitchfork-and-Torch wants to merge 19 commits into
Closed
Stop RankingScorer author diversity from keying the retweeter#54Pitchfork-and-Torch wants to merge 19 commits into
Pitchfork-and-Torch wants to merge 19 commits into
Conversation
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
RankingScorer author-pool decay used the wrapper author_id. Phoenix already hashes get_original_author_id, so one original could flood For You through distinct retweeters while a single retweeter of distinct authors was decayed. Count diversity on the original author. Co-authored-by: Jon Bailey <Pitchfork-and-Torch@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug
RankingScorer::author_pool_countsdecayed on wrapperauthor_id. Phoenix ranking features already key the original author (as_tweet_info/get_original_author_id). Distinct retweeters of one original did not share a diversity bucket. One retweeter of distinct originals did.This is not #31 (author-size IPS). This is not xai-org#125 (gizmoduck origin size/NSFW). This is not xai-org#128/xai-org#154/xai-org#135 (in_network stamps).
in_networkstays the poster. Diversity is the post-Phoenix author-repeat lever.Five-line proof
RankingScorer::author_pool_counts(EnableAuthorDiversity)PhoenixCandidatePipelinescorers[PhoenixScorer, RankingScorer, VMRanker]thenTopKScoreSelectorauthor_idwhile Phoenix hashedget_original_author_id()PostCandidate::as_tweet_info/build_tweet_infosalready send the original author to PhoenixChange
get_original_author_id()(retweeted user, else poster)retweeted_user_id)Tests
Standalone rustc model of
author_pool_counts+get_original_author_id: 3/3 passed.cargo testcannot run. Public dump has no home-mixer crate manifest.Fork PR: none