Repository navigation
Kindred 2.3.0
Kindred 2.3.0
2.2.0 gave the family a cookbook, a game of one's own and a feed. 2.3.0 makes the feed say what changed, moves the Campaign
onto an invented continent with a board worth coming back to, and lets one Kindred server host families for other people,
run by an operator who never reads their records. Try it on two invented families before installing anything:
kindred-demo.niklas-heer.workers.dev.
What's new for families
- The feed shows the new value. "Ada updated Carl: new phone number +49 30 …, born 3 May 1950 in Graz." A phone number
or email you can tap, an address that opens the map, the start of a biography, "Phone number removed". Each reader sees
only what they could see on the person's page now; old values never, and medical, allergy and faith notes are named by
kind only. See docs/feed.md. - The Campaign on an invented continent. A new continent each week, with invented names (checked against real places
and well-known fictional ones) and real terrain: marshes hold few troops, an attack across a river or by sea takes two
rounds, mountain ridges close a border. The family's houses are your rivals. Marches, battles and conquests are animated,
and a reign ends with a chronicle and a title. On a phone the turn, Undo and "End the turn" stay at hand. - One reign a day counts. The first reign you begin each day is the one the family's table ranks; it is kept as you
play, so you can continue it on another device. More reigns are practice and still show your personal best. Each score
shows the renown and quiz advantages behind it. See docs/campaign.md.
Hosting families for other people
- The operator. An instance role, separate from every family's roles. The console at
/operatorlists the families
(size, storage, stewards, status; never their records), makes a family for someone with a one-time steward invitation
(the operator is not added), keeps the waiting list from the public request form, handles data requests from relatives
who never signed up and forwards them to the family's stewards, sets storage caps, can make a family read-only or close
it, and keeps an audit log. Operators can be told of new requests by push. - Who may make families: the operators only, any steward (as before, and the default on an existing install), or
anyone by request. New installs limit each account to five families. - Legal pages. An Impressum, privacy policy, terms and a report-content contact, written in the console, appear at
/legaland in a quiet footer. While there are terms, making a family or becoming its steward asks to accept them. - Families in Durable Objects on Cloudflare. A family gets its own SQLite-backed Durable Object the moment it is made:
no D1 binding, no redeploy, no limit of bindings, up to 10 GB each, optionally in the EU. Existing D1 families keep
working. A Deploy to Cloudflare button starts a new install.scripts/import-to-do.tsmoves a family in;
scripts/backup-do.tslets a steward download one.
See docs/hosting-many-families.md, with a short checklist of what running a server for
other families involves in the EU (not legal advice).
Upgrading
Back up first. This release adds seven migrations:
migrations/tree0035 and 0036: the Campaign's rulesets, and the counted reign fixed when it begins. Apply them before
the new code serves.migrations/accounts0033 to 0037: Durable Object families, the operator, requests, imports, closed families and terms.
On Node they are applied when the server starts, after a copy of each database. On Cloudflare, mise run deploy applies
them before the new Worker goes live. To go back to 2.2.0, restore those copies and start the old version.
Things to know:
- Your earliest account becomes the server's operator. Nothing else changes for a self-hosted family:
family_creation
staysstewards, there is no family limit, and the legal links stay hidden until the operator writes them. - Earlier Campaign reigns are kept and listed apart (an earlier ruleset); they are not compared with the new ones. A
reign in progress in an open tab under the old rules is let go with a short message. store.treeIds()andstore.ensureTree()are async for anyone with code against the store.- New settings:
KINDRED_JURISDICTION,KINDRED_TURNSTILE_SITE_KEY,KINDRED_TURNSTILE_SECRET.
The full list is in the changelog.