[codex] expose hashed community watch signals#20
Draft
mashbean wants to merge 3 commits into
Draft
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
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.
Summary
/signals.jsonas a defensive, de-identified Community Watch signals exportPOST /signals/checkso downstream services can check text, contacts, and URLs without receiving raw source recordsverdict,confidence, and aggregatedmatchedSignals; cap request size to reduce abuse riskdocs/signals-api.mdValidation
pnpm typecheckCOMMUNITY_WATCH_API_URL=https://server.matters.town/graphql pnpm buildGET /signals.jsonreturned 347 records from production API with hashed sample fieldsPOST /signals/checkreturnedverdict: none,confidence: 0, and no raw content for a non-matching sampletexttype returns schema error