data portability now, and whether hosted accounts are ever a direction

[AlexCSalinas]

Small: there's no way to back up or move the database. It's one SQLite file on one machine, so losing the laptop means losing the history (which matters more here than most places) since the point is remembering people across sessions. A villain export / villain import-db pair fixes it, no accounts or server needed. Happy to PR it.

Big: is hosting/sign-in ever a direction you'd want, or is local-only permanent?

The interesting version isn't "log in to save your data" It's a home game pooling reads on the regulars they all play. Four people sharing a season on the same opponents beats what any one of them has, and small samples are the problem this tool exists to solve.

Not cheap, though: hand histories name other players who never agreed to be recorded, so hosting them is a real responsibility, and it makes the project something you operate rather than something people run. A cheaper version - let two people merge databases locally, reusing the identity matching that imports already do.

Mostly want to know if the door's open before anyone builds toward it.

cc @aroraarnav

[aroraarnav]

Agree on the privacy part — hosting hand histories that name people who never agreed to it is a much bigger lift than a tool that just reads your own machine. Not doing that yet.

Scoping this down for now: your own db, tied to a login instead of one laptop. No pooling, nothing about anyone else's hands changes. Basically the export/import idea but automatic — sign in, your db follows you. Going with Supabase for auth + storage, free at this size, nothing to run.

Pooled reads is the interesting version but it's the harder problem for the reason you gave, so it stays open rather than built toward until there's an actual answer on consent/visibility. Good to flag it now.