Storage

KEWEKE is local-first, so your lists live in your browser by default. Remote storage only exists for lists you choose to share.

In the browser — IndexedDBCopy Anchor Link

All personal data is in IndexedDB on your device:

• Lists live in a store keyed by their identifier. The app reads them sorted by last update, so the most recent list appears first.
• Identity (your userId, deviceId, keypairs, and display name) lives in its own store. It survives page reloads and is isolated per browser.
• Data you can clear — from /user you can clear local lists + identity (this browser only) or local lists for remote users — the service never deletes shared copies for other participants when you clear locally.

When offline, you still read and edit your lists. Edits queue as local mutations and are written straight to IndexedDB.

Browser stores are in the list store component and the identity store component.

On the edge — Durable Objects + SQLiteCopy Anchor Link

Each shared list is its own Durable Object with a small SQLite database:

• one row for the list metadata (title, revision, alias, owner)
• rows for active items and for recently deleted items
• rows for the last ~100 applied mutation IDs (for idempotency) and for item history

Because a Durable Object is single-threaded for its list, edits are applied one at a time and revision numbers stay sequential. If the object has never seen a list snapshot, importing one creates it; importing the same snapshot twice is idempotent.

The table layout and writeSnapshot / writeMutationDelta paths are in the KEWEKE list object.

How the app picks which copy to showCopy Anchor Link

• Opening /keweke/ reads IndexedDB only — it shows your catalog, no network.
• Opening /keweke/:listId first tries the local copy, then falls back to the remote snapshot via the server loader. A remote snapshot can become a cached copy in IndexedDB so later opens still feel instant.
• Remote lists that disappear (owner deleted, or permission revoked) are removed from your local catalog on next sync.

Sharing and aliasesCopy Anchor Link

A list's address is its identifier. Optionally, after you rename a local list the service can mint a short friendly alias; otherwise the raw identifier is the URL. Aliases are resolved via the same directory that registers new lists.

Alias handling is in the alias component.