| Q1 |
Does Fastmail serve JMAP EventSource push to API-token clients, and what are its JMAP rate limits and maxObjectsInSet? |
| Q2 |
Does Fastmail accept arbitrary Tandem-* headers via Email/set, and return them unchanged on Email/get? |
| Q3 |
Folder size: how do Fastmail and Dovecot behave with ~100k messages in one folder (Tandem's expected upper bound per hub)? |
| Q5 |
Backup key format: base32 groups (§6.3) or a word list (easier to write down, adds a list to every SDK)? |
| Q9 |
Padding message sizes to hide content length from the hub. |
| Q10 |
Tombstones are kept for good (§12.3). Is that affordable at Liszto's deletion rate, or does v1 need a safe way to drop them? |
| Q14 |
model/owner_model.py and model/test_owner_model.py model the collection rules: the owner's key as the only authority, epoch identity, fixed inventories, dead collections and how the news spreads, signing again, crash-resumable rotation, and the owner's devices coordinating through home, with a randomized run of three devices, crashes and decisions. Keys and signatures are symbols, not cryptography. Not modelled: the mail bindings, pairing and its code, invitations and UX. tandem_model.py and rotation_model.py are models of withdrawn designs (§19) and say nothing about this one. |
| Q15 |
A stolen device or a found backup key can't be cut off; the user starts over (§6.4). Per-device keys would fix that. They were designed three times in this draft's history and never came out sound (§19), so they are left for a later version. |
| Q16 |
A roster gains one complete statement per change and is copied at every rotation, and an inventory keeps entries for writes no rotating device has seen (§8.3). Is a signed checkpoint needed for long-lived collections? It would also have to carry who came in through which invite and has since gone, which devices now read from the full chain (§11.3). |
| Q20 |
Two devices of one owner changing a collection's sharing in the same moment kill it (§11.7). The note in home makes that unlikely. If it happens in practice, a designated device per collection is the known fix (§19). |