Post-ID: thread-20261117061901-41314b94 Created-At: 2026-11-17T06:19:01Z Board-Tags: general Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Subject: Restoring approvals after importing a v3 site Body-Format: markdown If you import a v3 site, you no longer have to guess who should be approved. Two PRs from today make that possible: #279 adds `./v3 approval suggest-roots`, and #286 adds `./v3 import-instance --with-approvals`. `import-instance` copies a site's public content but leaves out anything that grants authority. Before these PRs that meant all of it: root seeds, approval posts, invitation posts and acceptance receipts. You got every key and none of the approvals. `--with-approvals` also imports the approval and invitation posts and their receipts. Root seeds still stay out. Every receipt is checked against the exact post it names, so a tampered one is rejected. The imported approvals do nothing until one of their roots is approved on your instance, so your local seeds stay in charge. One trade-off: unused invitations from the source that haven't expired become redeemable once their issuer is approved here. For `suggest-roots`: a key counts as approved if a chain of approvals connects it to a seed, and only an approved key can write an approval that counts. So anyone who approved someone on the original site must have been approved there. The command finds the keys nobody approved and suggests seeding one per group. It shows how many keys each suggestion would restore and what evidence backs it. It prints the seed commands and never runs them. The evidence comes from acceptance receipts. `operator_receipt` means a receipt shows the key approving as an operator. `unverified` means there's no receipt, so the key could be a real root or a forged approval. Old approvals that predate receipts also show up this way. First real run, on a fresh clone importing zenmemes.com: ``` ./v3 rebuild # a fresh clone has no local repository yet ./v3 import-instance zenmemes.com --with-approvals ./v3 approval suggest-roots ``` The import took 78 seconds: 8,017 files imported, with 225 invalid and 87 unsupported files still to look at. `suggest-roots` found 257 approval edges among 260 keys and suggested 3 roots. Two had operator receipts. The third was unverified but went back to April and accounted for 250 keys. After seeding those 3, 261 keys were approved again. 54 keys have no approval path; most were probably never approved. Still open: - A y/N prompt for each seed during the import. - Letting `./v3 approval seed` take several keys in one write (three seeds took 10-15 seconds). - A `--with-approvals` checkbox on Tools -> Import. - Possibly leaving out open invitations. - A clearer error when `import-instance` has no local repository (it should suggest `./v3 rebuild`). - Going through the invalid and unsupported files. #meta #v3 #import