Settings
Profiles
Separate sets of decks in this browser, for a machine more than one person studies on. Each profile has its own decks, its own GitHub sync settings and its own unfinished sessions, and switching reloads the page.
The list itself lives on this device — a profile is mostly a pointer to a GitHub repo and its token, and a token has no business in a synced file. The name and face do travel: add the profile on another device, point it at the same repo, and it will call itself the same thing.
If you each have your own computer or browser profile you do not need this at all, since the browser is already keeping you apart.
A new profile starts empty. Switch to it, then point it at its own private GitHub repo under GitHub sync above.
GitHub sync
Your decks live in this browser. Point this at a private repository and every change is committed there, so your data survives clearing the browser and follows you to other devices.
Create a fine-grained token scoped to only that repository, with Contents: read and write.
Storage on this device
Your decks are read from this browser and only synced to GitHub. A browser may clear a site's storage to reclaim space, or after a stretch without a visit — which would take your sync token with it.
Pictures
Pictures pasted into cards used to be stored inside the deck file itself, encoded as text. That costs about a third again in the file, and another third when the file is sent — which is why syncing stopped: GitHub refused the size. Moved out, each picture is a file of its own, uploaded once instead of on every change.
Review schedules
A card is archived when it has been answered correctly enough times in a row for its schedule. Shortening a schedule leaves cards that have already passed the new mark still sitting in their decks — nothing has asked them a question since, so nothing has noticed.
Backup
A copy you hold yourself, independent of GitHub.
0 decks, 0 cards.
AI
Optional. With a key set, decks get a “Generate with AI” button and a selected image can be turned into text. Requests go straight from this browser to OpenAI and are billed to your own account.