feat(nip56): add WoT-weighted content reporting - #770
Open
Priyanshubhartistm wants to merge 2 commits into
Open
Conversation
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
🦋 Changeset detectedLatest commit: 93d2a4c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Collaborator
|
coverage: 72.449% (+0.2%) from 72.235% — Priyanshubhartistm:feat/content-reporting into cameri:main |
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
2 participants
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.
Description
Accepts and stores kind-1984 NIP-56 report events (
p/etags identifying the reported pubkey and/or event, plus a standard report type spam, nudity, illegal, impersonation, malware, profanity, other). Each report is scored by the reporter's WoT distance fromwot.seedPubkey: a direct follow gets full weight, weight halves each additional hop, and a pubkey outside the trust graph entirely gets zero stored, but scored near zero as intended.A new
nip56.trustedModeratorspubkey list gets maximum weight regardless of distance, and a report from one of those pubkeys is flaggedactionablein thereportstable. This PR records that flag but does not yet execute any automatic action (hiding content, deprioritizing in query results) that's left for a follow-up PR once there's a consumer for it, such as an admin/management API for reviewing and acting on reports.The report event itself is always stored and broadcast normally, independent of the
nip56feature flag; only the scoring/recording step is gated behindnip56.enabled(disabled by default).Related Issue
Closes #769
Motivation and Context
The NIP-56 spec itself warns against automated moderation driven by public reports, since a coordinated handful of accounts can game a naive report count. Tying report weight to WoT distance from the operator's trust circle means random/unknown reporters score near zero, while reports from within the trust circle (or an explicitly configured moderator) carry real signal.