Understand Epheme — a tiny story about feedback
Scenario: a new developer wants a simple feedback flow: “User sees something → clicks ‘Give feedback’ → writes it → done.” No accounts. No dashboards. Nothing else. But in 2026 that innocent desire usually turns into a monster.
Path A — The "Normal" Web Way
1. You start simple
Add a feedback form (Name, Email, Message). You think: “I’ll just email myself the submissions.”
2. Then you need persistence
So you add a database, a `feedback` table, and an admin view. Now you’re storing user data — privacy and access become concerns.
3. Then you need identity
Users want to see/edit their past feedback or get replies. So you add accounts, login, password resets, email verification — you’ve built a user system not a feedback box.
4. Then you add third-party identity
“Sign in with…” brings OAuth, client IDs, secrets, callback URIs, tokens. All of that for a feedback box.
5. Then you need policies
With accounts and stored data you must add privacy policies, retention rules, cookie banners, DSAR handling. Your simple tool turned into a platform.
Path B — The Epheme Way
1. The same desire
“User sees something → clicks ‘Give feedback’ → writes it → done.” You refuse to cross the identity line.
2. No accounts
No login. No email. No user profile. You don’t need to know who they are to hear what they think.
3. Use Epheme primitives
Each device generates a keypair. Feedback is signed by the device key. The app gains continuity (same device) without identity (who the person is).
4. Choose where feedback lives
Options: Pure local (stays on device), ephemeral Hub (signed objects stored without accounts), or Hybrid (mirror locally and to a Hub). Replies can be delivered via ephemeral channels or one-time links — no login required.
5. Never cross into identity
No OAuth, no account tables, no password resets. You only need signed feedback, a viewer, and optional ephemeral reply channels.
Path A vs Path B (short)
Path A — Normal Web
Feedback → accounts → auth → identity providers → policies → platform.
You own data you never wanted and inherit complexity you never asked for.
Path B — Epheme
Feedback → signed objects → optional hubs → no identity → no accounts.
You hear from users without owning them; surface area is small and sane.
“You don’t have to build an identity system just to let people talk to you.” Epheme gives device-level continuity, signed feedback, optional hubs, and ephemeral channels — same outcome, far less cost.