Skip to content

Stop user-cred from counting reverse linked-account edges - #165

Open
Pitchfork-and-Torch wants to merge 1 commit into
xai-org:mainfrom
Pitchfork-and-Torch:cursor/user-cred-linked-edges-21ef
Open

Stop user-cred from counting reverse linked-account edges#165
Pitchfork-and-Torch wants to merge 1 commit into
xai-org:mainfrom
Pitchfork-and-Torch:cursor/user-cred-linked-edges-21ef

Conversation

@Pitchfork-and-Torch

Copy link
Copy Markdown

Bug

filterLinkedUserEdges exists to keep linked-account pairs out of UserCred PageRank. It joined follow and engagement edges on the exact ordered pair (userId, linkedUserId) from AccountExpansionInvestigations.

That dataset is an undirected investigation pair, not a graph edge. Flock follows and 7-day fav/RT edges are oriented the other way: follower→followee, engager→author. Mass flows that same direction.

Proof

  1. Investigations row is (mainId, altId).
  2. Alt follows / likes / RTs main → edge (altId, mainId).
  3. Join key (altId, mainId)(mainId, altId) → edge kept.
  4. PageRank pushes mass follower→followee, so alts pump the primary.
  5. Published score feeds isHighPageRankV2 / cred.score. Abuse enforcement skips on cred.is_high || cred.score >= 50. Safety-label user-agg excludes high page-rank users from NSFW account labels.

Main→alt was the only direction dropped — the one that does not inflate the primary.

Fix

Emit both orders of each linked pair (skip self-pairs). filterLinkedUserEdges is unchanged. If the snapshot already stores both directions, the extra keys are a no-op.

One file: user-cred-v2/UserCredV2App.scala.

Not a home-mixer / VF / Thunder change. Not a fork PR.

Account-expansion pairs are undirected. Matching only
(userId, linkedUserId) left alt→main follows and engagements in
the PageRank graph, so linked alts could still pump mass into
the primary account.

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.

2 participants