decide: owner's picks recorded — all 8 decided, threading and email links pulled into v1

decisions/2026-11-01-comments-reactions/notes.md

+# Decision notes — Comments & reactions for me.nech.pl
+
+Date: 2026-11-01 · Review: 
+
+> Verdict: Self-hosted comments + reactions as a nechapi service on erable — SQLite, approval-queue antispam, no captcha — is the recommendation; the open questions are identity warmth and how much lands in v1.
+
+## DP1 — Comments architecture
+
+**Chosen: A — Self-hosted comments API on erable via nechapi** (recommended)
+
+## DP2 — Antispam without captcha
+
+**Chosen: A — Layered friction + moderation queue** (recommended)
+
+## DP3 — Identity & attribution
+
+**Chosen: A — Name + optional email (never displayed beyond name), no accounts** (recommended)
+
+## DP4 — Reactions
+
+**Chosen: A — Same service, separate endpoint, no moderation** (recommended)
+
+full emoji set, sorted by already used, or a selection ill provide (no poop no vomit etc but yea smile grin heart thumb up etc idk maybe we keep usedul values clusters only? fb did a solution not fan but lets build ours?
+
+## DP5 — Storage & durability
+
+**Chosen: A — SQLite file on erable + nightly dump into the existing backup regime** (recommended)
+
+## DP6 — Rendering & caching model
+
+**Chosen: A — Client-side fetch + noscript fallback note + cached JSON** (recommended)
+
+A + some last comments or top comments jaked static plan b nice progressive enhancement. and indeed comments need upvote/downvote reaction and threaded comments if we want.
+
+## DP7 — Moderation UX for the owner
+
+**Chosen: A — Approve/reply/flush via a tiny token-gated admin page on api.nech.pl** (recommended)
+
+A and email and i can click easy links to accept/reject
+
+## DP8 — Reply/notify (v1 scope)
+
+**Chosen: B — Threading v1** (differs from recommendation)
+
+---
+
+Progress: 8/8 decided.
\ No newline at end of file