0x00 한

Research / Daily reports

  • Sources read: 1
  • Canon files updated: 1
  • Radar entries: 0
In one lineX lowered the weight of share via copy link in the home-mixer weights mirror from 20.0 to 0.0. The vm-ranker mirror remains at 20.0.

Source xai-org/x-algorithm@590f392 — xAI, 2026-11-13, code. In these notes' numbering, this is Gen4+Gen63.4+N is the number these notes assign in order to commits after the 2026-08-13 Gen4 release).

Background In X For You, Phoenix (a Grok-based Transformer ranker) predicts the probability of actions such as like, reply, and share for each candidate post, multiplies each probability by a per-action weight, and orders posts by the sum. X publishes the production defaults of these weights as a cron mirror (a script that copies the production configuration into repository code every day); since 2026-09-23 the mirror has been split into two files, one for home-mixer (the service that receives feed requests, gathers candidates, and scores them) and one for vm-ranker (a separate service that computes the weighted sum and DPP re-ranking). Until now, share via copy link was 20.0 in both mirrors, the largest of the positive weights. This commit reflects the 2026-11-12 sync, lowered this weight in the home-mixer mirror to 0.0, and added a new ordering mode to DPP, off by default.

What we learnedA. Share via copy link no longer contributes to the score in the home-mixer mirror

  • The share via copy link weight in the home-mixer mirror changed from 20.0 to 0.0 verified — home-mixer/params/param.rs:495-500
    • The parameter is ShareViaCopyLinkWeight (rust_home_mixer_share_via_copy_link_weight), and the sync time in the file header changed from 2026-11-11T16:00:37Z to 2026-11-12T16:00:36Z.
  • The same weight in the vm-ranker mirror remains at 20.0 verified — vm-ranker/params.rs:34-39
  • For requests that vm-ranker answers, the local weighted sum in home-mixer is overwritten by the vm-ranker score, so 20.0 is likely still used for the main feed order inferred. The basis is that the home-mixer VMRanker scorer first computes the local weighted sum and then overwrites it with the service score (services/x.md ranking section).
    • The home-mixer weighted sum is used as is in paths such as the fallback score for requests where the vm-ranker call fails verified (services/x.md diversity section).
    • In the 2026-11-04 sync (Gen4+57) as well, seven weights changed first in the home-mixer mirror only. The order may be that home-mixer changes first and vm-ranker follows inferred.

What we learnedB. A mode where DPP suppresses candidates resembling posts higher on the page was introduced, off by default

Until now, DPP (determinantal point process, a diversity technique that selects items as a set so that similar items are not picked together) chose by looking only at the top candidate set, then re-sorted the chosen candidates by score before emitting them. This commit added two options.

  • An option to emit results in the order DPP picked was added. The scores are reassigned to match the ranks verified — vm-ranker/dpp.rs
    • The switch is DppGreedyOrder and its default is false (vm-ranker/params.rs:260-271).
    • The ith picked candidate receives the ith highest raw score among the chosen candidates. As a result, the DPP order is preserved even if a later stage re-sorts by score.
  • The sliding-window mode suppresses candidates that resemble posts placed in the few slots directly above with a penalty that weakens with distance verified — same file.
    • The switches are DppWindow (window size; off if the default 0) and DppWindowHalfDistance (default 0.0).
    • Posts emitted within the previous 10 minutes in earlier responses are used as the front of the window. The switch VMRankerSendDppHistory, with which home-mixer loads this history, is also false by default (up to 200 posts).
    • The gain of a candidate is computed with the formula below, and at each slot the candidate with the largest gain is picked.
gain(c) = exp(2α · score(c) / max_score) × Π_d (1 − w_d · cos²(c, post d slots above))
w_d = 0.5^(d / half_distance)   (if half_distance = 0, w_d = 1)
α = θ / (2(1 − θ))
  • A test confirms that the window effect disappears when the history is older than 10 minutes verified — vm-ranker/scoring/dpp_model.rs
    • With a history from 1 minute ago the order becomes [9, 5, 10], and with a history from 11 minutes ago it becomes [10, 5, 9], the same as with no history.

What we learnedC. A label that separately judges spam promoting shares was introduced

The PtOS (post-level safety policy judge) path of grox (a Grok-based nearline classifier that attaches safety annotations to posts) attaches the SpamHighRecall label depending on the spam violation type. This label is read by the filter rules of recommendation surfaces.

  • Spam promoting clicks, replies, and shares each became a separate policy type verified — grox/flows/ptos/state.py
    • The type names are SpamPromotesClicks, SpamPromotesReplies, and SpamPromotesShares.
  • Only the share-promoting type attaches SpamHighRecall, and it does not exempt high page-rank accounts (accounts with high PageRank-based trust) either verified — task_write_safety_post_annotations_result_sink.py
    • The existing types that receive the same treatment are EngagementBaiting, EngagementFarming, and CardManipulation.
    • Click- and reply-promoting spam receives only the PromotesClicks and PromotesReplies labels without SpamHighRecall, and share-promoting spam also receives PromotesShares.
    • The filter rules that read the three new labels, and the prompt changed so that the judge model emits these types, are not in this diff.
  • A test in abuse-enforcement-service (a service that takes account and post actions based on model scores) includes an example where the link-copy-bait detection head attaches SpamHighRecall verified — abuse-enforcement-service/service-lib/src/service.rs
    • The head name is CopyLinkBaitEmbeddingGrokDistilled. This commit also made the label record the name of the detection head that attached it.
  • Lowering the share via copy link weight and adding the share-promoting spam verdict appear to respond to the same problem, namely posts aimed at shares exploiting the ranking inferred. The basis is that both changes came in the same commit and that a link-copy-bait detection head exists.

What we learnedOther changes

  • When a safety label lookup fails for any reason, the verdict uses the expired cached label if one exists. Previously this applied only during a label cache outage verified — safety-label-source/source.rs
    • The lookup is cut off 5 ms before the caller deadline, and keys that run past the time are also treated as failures and answered with the expired label.
  • For like and repost notifications on my reposts, the original post is also judged, and if the original is filtered, the notification is not sent verified — visibility-filtering/post_evaluator/notification.rs
  • An option was added to the Phoenix ranker that reduces the attention contribution of the most recent 15 minutes, or of the 5 most recent positive history items within 2 hours. The default multiplier is 1.0, so it is off verified — phoenix/xrex/models/recsys_model.py
  • The response diversity metric gained SID (semantic ID, an id that represents a post as a hierarchical code) entropy that joins the recent 3-, 10-, and 30-minute history with the previous page verified — side_effects/response_diversity_stats_side_effect.rs
    • The windows overlap the 10-minute history of the DPP window mode, so this appears to be a metric for evaluating that experiment inferred.
  • A flow was added that splits posts with more than 4 media items into groups of 4 and sends them to the PtOS judge. It runs only if the generator exists in the deployment config verified — grox/flows/ptos/task_safety_ptos_many_media.py
  • Retrieval training dataset kinds for 1-, 2-, 7-, and 14-day windows, built from the AI video detection model results, were added to the proto verified — recsys.proto
  • The minimum number of posts before ads start being inserted into the Following feed changed from a constant to a switch. The default is 5, the same as the previous constant verified — home-mixer/params/param.rs:1031-1036
  • A switch that specifies the list of clusters not to compress in Phoenix retrieval calls was added, with an empty list as the default verified — same file, lines 279-284.
  • A cache was added to the AI trend feedback context lookup. It keeps entries for 5 minutes when a trend exists and 30 seconds when it does not verified — candidate_hydrators/ai_trend_feedback_context_hydrator.rs

Canon update In the weights table of services/x.md ## Ranking, we corrected the share via copy link row with the values of both mirrors and the reference commit, and added one line to that section's change log list. We added a sequence option and a sliding-window bullet to the VMRanker DPP item in the diversity section. In the safety section, we added an expired-label fallback bullet and, under the Labeling Rules list, a PtOS promoted-spam policy bullet. In ## Sources, we raised the reference commit and commit count to 590f392 and 63, and added one row to the change log summary table.

Why it matters X lowered share via copy link, the largest positive weight since the 2026-08 release, to 0 in one mirror. Because the vm-ranker mirror remains at 20.0, it is not yet known whether the actual main feed order changed, so we leave it as an inference. The DPP window mode appears to prepare a shift of the goal from "diversity within a set" to "diversity among posts seen in succession on screen", and because it is off by default, current behavior is unchanged.

What to check next