aboutsummaryrefslogtreecommitdiffstats
Commit message (Expand)AuthorAgeFilesLines
...
* federation: events offered to a node's store, and its operator's dropstv6 days2-2/+84
* docs: members by the fold are builttv6 days1-10/+12
* api: in a swarm holding a store, a node takes no token another issuedtv6 days3-2/+50
* topology: neighbours among the members of a node's own party, and of parties ...tv6 days5-1/+105
* topology: in a swarm holding a store, neighbours among its memberstv6 days1-0/+25
* peer: in a swarm holding a store, its members onlytv6 days5-0/+94
* handshake: the party its sender is oftv6 days4-3/+33
* federation: the members a node's store namestv6 days1-2/+34
* members: a node's entry names its partytv6 days1-1/+42
* node: a swarm holding a store has no swarm key, nor protocol writerstv6 days1-0/+24
* node: the party a node of a swarm holding a store is oftv6 days4-17/+95
* access: a put at an event's key held already, judged as made by handtv6 days2-18/+18
* docs: what of the store on Automerge is builttv6 days1-9/+14
* federation: a pinned checkpoint, found in the documenttv6 days4-13/+160
* store: the checkpoint at heads a store holds, as it builds one moving theretv6 days1-10/+33
* federation: events put againtv6 days2-8/+192
* federation: the store read from the documenttv6 days11-4/+425
* store: a store read anew refuses what its node refused of its owntv6 days1-0/+54
* node: a swarm holding a store, started from its root or joined by its IDtv6 days10-4/+326
* access: what a change of a swarm holding a store writestv6 days5-0/+311
* access: the policy of a swarm holding a storetv6 days2-16/+113
* document: a store swarm's genesis change, built byte for byte from its roottv6 days3-0/+181
* store: a fold names itselftv6 days3-0/+8
* docs: the federation's fold is builtdesigns/federation-1-stage-2tv6 days3-19/+21
* federation: fixed bytes of events, versions, roots and sizestv6 days2-0/+127
* federation: properties over generated federationstv6 days2-0/+576
* federation: the model, a second reading of the federationtv6 days2-0/+532
* federation: the JCS test asks escapes JCS doesn't write, as escapestv6 days1-2/+4
* federation: a test for each attack marked unittv6 days2-0/+1184
* federation: the federation as the store's foldtv6 days3-1/+947
* federation: events and checkpoints as bytes, and a harness that signs themtv6 days3-0/+610
* federation: versions, their rules, and the paths they matchtv6 days2-0/+539
* federation: keys, node IDs and signatures, each spelled one waytv6 days2-0/+148
* federation: JSON written one waytv6 days2-0/+452
* store: a fork refuses what the store it came from builds on what its root keepstv6 days1-1/+2
* federation-tests: vectors for JCS's order of names, and for the sizestv6 days1-4/+7
* store: a fork's later change ends once its events reach 1 MiBtv6 days1-4/+5
* store: documents parted by a writer's two changes come together at the next r...tv6 days1-2/+4
* store: grinding epoch IDs moves the nodes again for each lower onetv6 days1-1/+1
* store: a node follows no epoch with another policy, and reads nothing closed ...tv6 days1-8/+10
* store: the fold says how large an event may be, and the document judges by ittv6 days4-3/+20
* store: where a pinned checkpoint comes from, and what a node keeps across a r...tv6 days1-8/+16
* store: a node follows no epoch whose snapshot holds an earlier checkpointtv6 days1-8/+12
* store: one rule for putting events againtv6 days1-24/+29
* store: the snapshot is the store read from the document up to the basetv6 days2-9/+11
* federation: a client writes its record of votes before it sends onetv6 days1-6/+8
* federation: an event whose history holds two versions changing one is refusedtv6 days1-1/+2
* federation: what a checkpoint keeps is read as written under its versiontv6 days1-2/+5
* federation: a node is still joining until it synced with every seedtv6 days1-5/+7
* federation: whether a checkpoint passed is the operator's to knowtv6 days1-5/+6