summaryrefslogtreecommitdiffstats
Commit message (Expand)AuthorAgeFilesLines
* federation: a limit on the writers a user's nodes starttv8 days1-30/+52
* federation: only changes Automerge itself writestv8 days1-18/+41
* federation: several roots, final names, every voter countstv8 days1-820/+1168
* federation: all users are those there when a remake is proposedtv8 days1-36/+46
* federation: voters named at a remake, versions, what is uncoveredtv8 days1-127/+216
* federation: lines, time from the stamps, the last decision holdstv8 days1-493/+624
* federation: the fractions are numbers, a decision can be refusedtv8 days1-121/+169
* federation: numbers without constraint, names by a decisiontv9 days1-171/+164
* federation: the answers to its open questionstv9 days1-218/+387
* federation: a design for a swarm kept by parties that don't trust each othertv9 days2-0/+1255
* screen: `Screening::of`'s doc on `of`tv4 days1-1/+1
* screen: a test's actor named through `document`tv4 days1-1/+1
* screen: what is at the policy's place found in every map on the waytv4 days2-5/+87
* docs: the strict remake among the kindstv5 days2-3/+4
* screen: what reads as no policy has what is received judgedtv5 days1-5/+47
* docs/access: a strict policy given at genesis in the exampletv5 days1-3/+5
* state: a strict policy written where none judges, refused before it leavestv5 days2-5/+26
* remakes: a map made on the way names no group's usertv5 days1-10/+79
* policy: strict only where its values is a stringtv5 days2-34/+35
* remakes: a group named for the change it goes astv5 days1-12/+3
* config: a strict bootstrap policy found as the document reads ittv5 days2-8/+14
* store: the policy's reading unmarked however it endstv5 days1-3/+9
* policy: read only as continuum writes ittv5 days3-16/+72
* remakes: of one change, its other writes replayed before its linkstv5 days2-5/+23
* rules: a swarm turns strict only at its start or through a strict remaketv5 days5-278/+91
* config: a strict swarm starts emptytv5 days2-7/+16
* continuum-signed: its reading of an envelope is best efforttv5 days1-1/+3
* store: one reading of the policy's placetv5 days1-48/+75
* remakes: other writes replayed with the links by historytv5 days2-24/+113
* rules: the changes that turned a swarm strict found once for its headstv5 days2-20/+58
* rules: a strict swarm stays stricttv5 days2-25/+57
* access: a new swarm's policy where it starts from contenttv5 days1-1/+3
* continuum-signed: an envelope read as the server reads onetv5 days1-15/+36
* rules: the document's own policy read once for its headstv5 days1-4/+19
* store: values ordered by seq as the policy a read shows saystv5 days2-25/+86
* remakes: a signed place already held is kept like any write that losestv5 days2-11/+20
* remakes: links replayed in the order their changes were madetv5 days2-33/+149
* remakes: a chain replayed to what its part of the replay ends attv5 days1-4/+51
* rules: the time before strict is the change that turned it, written again or nottv5 days4-42/+146
* access: what revoking doesn't stop under a strict policytv5 days1-3/+10
* store: a signed value chosen by seq is named sotv5 days4-8/+18
* rules: nothing added to the time before a swarm turned stricttv5 days3-1/+104
* swarm: a new swarm's policy recorded in its genesis changetv5 days9-4/+98
* remakes: values signed by their users replayed as chainstv5 days2-3/+405
* store: counters and the API's placement go by what a read showstv5 days2-6/+52
* store: values ordered by seq only where the policy asks for signed valuestv5 days2-15/+96
* api: a signed write after the last seq there is a conflict, not a panictv5 days1-1/+1
* signed values: one reading of an envelope, everywheretv5 days8-139/+208
* signed values: value and meta apart, numbered; the highest seq is readtv5 days13-107/+370
* simtest: hyparview's views settle within a reaffirm roundtv7 days1-1/+11