docs: record useSpotCommunityScore aggregation
This commit is contained in:
parent
0e4e8c548a
commit
1a9a5ae967
1 changed files with 10 additions and 1 deletions
11
AGENTS.md
11
AGENTS.md
|
|
@ -717,7 +717,16 @@ session with **no other memory of this project**. So:
|
|||
the submit button is disabled) — a typo rarely has a photo. (2) The spot page
|
||||
shows a **Community verified / Unverified** badge computed from signals only
|
||||
*other* skaters can produce: community photos + `useSpotStatus` `reporterCount`
|
||||
(kind 2259). The weather score was renamed **"Conditions · weather only"**
|
||||
(kind 2259). **Community confidence aggregation (2026-10-03):**
|
||||
`src/hooks/useSpotCommunityScore.ts` does ONE batched query for a spot's
|
||||
engagement (photos 1063, status 2259, comments/tag-suggestions 1111, reactions
|
||||
7, zaps 9735, collections 30003), counts **distinct accounts** (never the
|
||||
mapper), tier-weights costly signals (zap 3, photo/status 2, rest 1) with a
|
||||
**per-account cap of 3**, and multiplies by each actor's **web-of-trust + real
|
||||
activity** (`useBatchTrustScores`/`useBatchActivity`) so a ring of empty
|
||||
accounts can't inflate it. Returns `level: unverified | seen | community` +
|
||||
breakdown; `SpotDetailPage` shows a "why" line (`2 photos · 1 zap …`). The
|
||||
weather score was renamed **"Conditions · weather only"**
|
||||
(in `SpotDetailPage` and the `SpotMap` popup) so it can't read as spot quality.
|
||||
(3) `useNotASpotReport` = one-tap **NIP-56 (1984)** report tagged
|
||||
`not-a-skate-spot` (NIP-56 `other` reason + our `L`/`l`/`t` taxonomy), used
|
||||
|
|
|
|||
Loading…
Reference in a new issue