Skip to content

Stop SubscriptionHydrator from skipping exclusive ids on retweets - #40

Closed
Pitchfork-and-Torch wants to merge 19 commits into
mainfrom
cursor/subscription-hydrator-original-id-cd6f
Closed

Stop SubscriptionHydrator from skipping exclusive ids on retweets#40
Pitchfork-and-Torch wants to merge 19 commits into
mainfrom
cursor/subscription-hydrator-original-id-cd6f

Conversation

@Pitchfork-and-Torch

Copy link
Copy Markdown
Owner

Phoenix SubscriptionHydrator asks TES for exclusive authors by wrapper tweet_id. Super Follow lives on the original. A retweet wrapper is not exclusive, so subscription_author_id stays None and IneligibleSubscriptionFilter keeps the card.

  • Entry: Phoenix SubscriptionHydrator (phoenix_candidate_pipeline.rs)
  • Sink: IneligibleSubscriptionFilter keeps subscription_author_id: None as public
  • Break: TES and cache keyed by candidate.tweet_id instead of get_original_tweet_id()
  • Viewer effect: subscriber RT of an exclusive post still serves on For You to non-subscribers
  • Twin: MediaInfoHydrator, LanguageCodeHydrator, EngagementCountsHydrator already fetch by original; QuoteHydrator is Stop QuoteHydrator from skipping quoted ids on retweets xai-org/x-algorithm#118

This is not xai-org#118 (quoted ids). This is not xai-org#129 (subscription-list miss). This is not xai-org#141 (TES fail-closed).

Look up and cache TES exclusive authors by candidate.get_original_tweet_id(). Native exclusive posts are unchanged. Two retweets of the same exclusive now share the cache key.

  • Native exclusive still keys TES by the candidate id
  • Retweet of exclusive keys TES by the original id (fails on unmodified main)
  • TES keyed only by the wrapper id does not treat the retweet as exclusive

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

Fork PR: none
Survey: xai-org#96xai-org#142. Unclaimed.

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
TES exclusive lookup and the hydrator cache were keyed by the wrapper
tweet_id. A retweet of a Super Follow post therefore looked like a
public tweet, and IneligibleSubscriptionFilter kept it.

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