You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
Phoenix predicts the probability that a viewer clicks the author's profile (README "Scoring and Ranking", Clicks: post · profile · ...), but RankingScorer multiplies that prediction by ProfileClickWeight = 0.0, so it adds nothing to the final score.
The default ValueModelMode is "weighted", so this is the live scoring path. The value has been 0.0 in every commit touching param.rs since 2026-08-17 (15 commits checked).
Was 0.0 chosen because the profile-click head is poorly calibrated, or to avoid rewarding curiosity-bait? If the latter, pairing it with dwell on the profile could guard against that.
Problem
Phoenix predicts the probability that a viewer clicks the author's profile (README "Scoring and Ranking",
Clicks: post · profile · ...), butRankingScorermultiplies that prediction byProfileClickWeight= 0.0, so it adds nothing to the final score.The default
ValueModelModeis"weighted", so this is the live scoring path. The value has been 0.0 in every commit touchingparam.rssince 2026-08-17 (15 commits checked).ProfileClickWeight= 0.0: https://github.com/xai-org/x-algorithm/blob/6bb4594/home-mixer/params/param.rs#L344ValueModelModedefault"weighted": https://github.com/xai-org/x-algorithm/blob/6bb4594/home-mixer/params/param.rs#L483FollowAuthorWeight= 4.0: https://github.com/xai-org/x-algorithm/blob/6bb4594/home-mixer/params/param.rs#L378Why it matters
Proposal
ProfileClickWeightin an experiment (somewhere betweenClickWeight= 0.4 andFollowAuthorWeight= 4.0).Open questions