Reduce Freebuff VPN false positives with Spur#714
Merged
Conversation
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
1 participant
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.
Adds Spur Context API as a required second opinion for Freebuff country/privacy gating so IPinfo-only proxy/VPN detections can be cleared while corroborated hard anonymizer traffic remains blocked.
Updates free-mode cache schema and migrations to persist Spur signals, normalized privacy decisions, provider disagreement categories, and safe TTL behavior including legacy-cache misses for pre-Spur hard IPinfo rows.
Adds chat and session logging/analytics for privacy tuning, keeps hard-blocked decisions uncached, and documents the new required
SPUR_TOKEN.Validation: focused Freebuff/Spur tests, web/internal/common typechecks, and
git diff --check.