feat: infer links regardless of Raider.IO ownership visibility - #34
Merged
Conversation
The sweep gated both its root and every candidate on Raider.IO ownership being public (`ownerId === null`). That condition cannot tell a player who withheld the link from a character never claimed on Raider.IO at all, and it excluded the latter — most characters, and precisely the bank and levelling alts the fingerprint exists to find. Maintainer's decision to remove both gates. This reverses the resolution of "Privacy stance on defeating hidden ownership" (#8) and drops the behavioural mitigation "Data-protection exposure for publishing derived account linkage" (#16) identified as the one that materially moves the UK GDPR balancing and necessity tests. Manual removal requests are now the only exclusion route, and suppression checks are unchanged. Removing the candidate gate also removes one unbudgeted Raider.IO request per roster member — hundreds per sweep, counted against neither the discovery cap nor the Blizzard hourly budget. /privacy no longer promises an exclusion the code does not make; the design spec carries an amendment and CONTEXT.md redefines the term. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qh8Zb2HnaxebWrRLUMoAiv
This was referenced Aug 10, 2026
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
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.
Replaces #33, which was left conflicting after #32 squash-merged. Same single commit, rebased onto
main.The sweep gated both its root and every candidate on
ownerId === null— Raider.IO ownership not being publicly linked. That one condition covers two unrelated states:characterDetails.usernullnullSampling arbitrary characters found the second state is the ordinary one, and it is exactly the population the fingerprint exists to reach — bank alts and levelling alts are the least likely characters to be claimed upstream. Both gates are removed.
This reverses a closed decision. Privacy stance on defeating hidden ownership resolved that privacy-hidden ownership excludes fingerprint-derived linkage, and Data-protection exposure for publishing derived account linkage named not publishing inferred-only linkage where a contrary preference was signalled as one of the two mitigations that materially move the UK GDPR balancing and necessity tests. A fingerprint-derived link may now connect characters whose Raider.IO ownership is not public. Maintainer's decision; recorded on both issues and on the map.
Also in scope, because the candidate gate was where it lived: each candidate cost one live
getCharactercall to Raider.IO — hundreds per sweep, counted against neither the discovery request cap nor the Blizzard hourly budget. Removing the gate removes the call, and a test now pins it./privacyno longer promises an exclusion the code does not make, and points at removal requests as the only route.CONTEXT.mdredefines privacy-hidden ownership.Both new handler tests were confirmed red against the previous code.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Qh8Zb2HnaxebWrRLUMoAiv