NEC-386: Website: Product › Features, a read-only feedback board on nectenda.com #354
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!354
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-386-website-product-features-a-read-only-fee"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-386 — https://projectron.nerchure.com/tasks/408
The feedback board's public, read-only pages on nectenda.com: /features (the list, with Sort and Filter as script-free
Every page is drawn from one snapshot of the public board (new GET /api/snapshot, computed at most every 10 s), kept at each Cloudflare location under one key: fresh for 60 s, with a 30 s grace while one request refreshes it in the background, behind a 15 s lease, and as a last good copy for a day, shown with its time when the board is down. So visitors' traffic cannot become the board's load; decided with the user after three reviews, each worked through (spec: docs/changes/NEC-386-features-board/spec.md). Other hosts (nectenda.pages.dev, previews) redirect to nectenda.com. HSTS joins _headers for the whole site.
Ride-along NEC-392: CI and the local gate now run site/'s own tests.
After merge, the user's steps are in docs/manual-testing.md: the Cloudflare rate-limiting rule, the status page push, and the live checks. /features shows its 'cannot be reached' text for the minutes between the site's deploy and the board's promotion.
Spec:
docs/changes/NEC-386-features-board/spec.mdAlso fixes NEC-392: Site tests never run on a pull request, only after merge in deploy-site.yml
Changelog
The Feedback page links to the board's new public, read-only pages at nectenda.com/features.
nectenda.com/features shows a count beside every status in its Filter menu. The board had no public per-status count, so each page would have cost seven board calls (the list plus six `?status=…&limit=1` totals), all from Cloudflare's addresses and so all against one 300-a-minute read limit. `GET /api/ideas` now carries `counts: [{ status, n }]`, counted over what everyone can see, whatever the request's filters and whoever asks. A hidden idea is not counted even in its author's answer, so the counts are one answer the website can cache for every visitor (BOARD-015). An array rather than a map keyed by status: a `planned` key reads as plan data to privacy.test.ts's walker, and mutation-checking the map form showed it failing there on `$.counts.planned`. Task: NEC-386 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EV8ztaXPLDwMdRRrgpAUyK5b720c46928a8ee4d720