| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | held: a node merges its store's heads beyond what an event may name | tv | 13 hours | 1 | -0/+5 |
| | | | | | | | | | | | | | | | | Past 64 heads, no event is above them all, and what is written builds on the earliest 64 alone: where nobody writes, heads apart stay apart, and a checkpoint naming them is never written. Under a revision with merge events, a node its party lists signs merge events with its node key where its store holds more heads than an event may name, each on as many as it may, the earliest taken first, until no more are left (`Holding::merge`). The worker does so a random wait after the heads first were too many, as it puts again what the document lacks, so that of the members few do at once. `federation.md` says so under Nodes, and the guides say what a node writes by itself and what its log says. | ||||
| * | files: a test's scratch directory goes when the test ends | tv | 30 hours | 1 | -2/+4 |
| | | | | | | | | `scratch_dir` gives a guard (`Scratch`) that removes the directory with all it holds when dropped, the test passing or failing. Each test keeps it for as long as it uses the directory; the dashboard's browser check writes its page into one. | ||||
| * | access: tokens | tv | 12 days | 1 | -0/+15 |
| | | | | | | | | | | ct1 tokens: who, how they logged in, a session, when they expire, and optionally a narrower limit; signed by the issuing node's key and taken by every member (a node ID is its key). Revocation by the registry as it stands when a request comes. Auth plan M2. | ||||
| * | allow creating all key files | tv | 2026-11-01 | 1 | -43/+15 |
| | | |||||
| * | move warn_if_readable_by_others to files module | tv | 2026-10-31 | 1 | -1/+1 |
| | | |||||
| * | tests: unify scratch dir logic | tv | 2026-10-31 | 1 | -10/+3 |
| | | |||||
| * | add identity layer | tv | 2026-10-27 | 1 | -5/+38 |
| | | |||||
| * | introduce node keys | tv | 2026-10-27 | 1 | -0/+155 |
