aboutsummaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Expand)AuthorAgeFilesLines
...
* federation: every base taken up, writers for one user, cuts as unvouchestv4 days1-292/+358
* federation: votes name a remake's base, a user's own name, writers per usertv4 days1-154/+206
* federation: a root is a user, an epoch's first change its root changetv4 days1-38/+39
* federation: what a cut brings back, what `prev` namestv4 days1-114/+132
* federation: carry records, refusing within a window, digests by two thirdstv4 days1-161/+228
* federation: what an operator does on its nodes is no part of ittv4 days1-90/+79
* federation: one base an epoch, sight decides alone, lists of voterstv4 days1-358/+477
* federation: a thousand writers a user, and what the limit doestv4 days1-2/+6
* federation: changes Automerge wouldn't write are refused todaytv5 days1-12/+13
* federation: why not an actor for every changetv5 days1-0/+18
* federation: a limit on the writers a user's nodes starttv5 days1-30/+52
* federation: only changes Automerge itself writestv5 days1-18/+41
* federation: several roots, final names, every voter countstv5 days1-820/+1168
* federation: all users are those there when a remake is proposedtv5 days1-36/+46
* federation: voters named at a remake, versions, what is uncoveredtv5 days1-127/+216
* federation: lines, time from the stamps, the last decision holdstv5 days1-493/+624
* federation: the fractions are numbers, a decision can be refusedtv5 days1-121/+169
* federation: numbers without constraint, names by a decisiontv5 days1-171/+164
* federation: the answers to its open questionstv5 days1-218/+387
* federation: a design for a swarm kept by parties that don't trust each othertv5 days1-0/+1253
* docs: the strict remake among the kindstv30 hours2-3/+4
* docs/access: a strict policy given at genesis in the exampletv32 hours1-3/+5
* policy: strict only where its values is a stringtv32 hours1-3/+3
* policy: read only as continuum writes ittv35 hours1-5/+8
* remakes: of one change, its other writes replayed before its linkstv37 hours1-1/+2
* rules: a swarm turns strict only at its start or through a strict remaketv37 hours1-23/+10
* config: a strict swarm starts emptytv37 hours1-3/+4
* remakes: other writes replayed with the links by historytv38 hours1-1/+2
* rules: a strict swarm stays stricttv38 hours1-24/+26
* access: a new swarm's policy where it starts from contenttv40 hours1-1/+3
* remakes: a signed place already held is kept like any write that losestv40 hours1-10/+11
* remakes: links replayed in the order their changes were madetv40 hours1-2/+6
* rules: the time before strict is the change that turned it, written again or nottv40 hours1-5/+10
* access: what revoking doesn't stop under a strict policytv42 hours1-3/+10
* store: a signed value chosen by seq is named sotv42 hours3-3/+5
* rules: nothing added to the time before a swarm turned stricttv42 hours1-1/+5
* swarm: a new swarm's policy recorded in its genesis changetv42 hours2-3/+11
* remakes: values signed by their users replayed as chainstv42 hours1-0/+6
* store: values ordered by seq only where the policy asks for signed valuestv42 hours1-2/+4
* signed values: value and meta apart, numbered; the highest seq is readtv46 hours3-15/+26
* relay: a STATUS's heads wait at least 50 ms before they are pulledtv4 days1-1/+2
* changes: no marktv4 days1-13/+13
* changes: no tabletv4 days1-2/+3
* screen: take only the operations transactions writetv4 days1-4/+8
* screen: refuse what Automerge's transactions never writetv4 days1-2/+4
* screen: a change refused after its checks stands in for nothingtv4 days1-1/+2
* screen: a twin of this node's actor switches it only signed with its keytv4 days1-2/+3
* screen: what is asked of a change, asked of its own historytv4 days1-4/+9
* screen: refuse changes Automerge wouldn't have writtentv5 days1-0/+6
* hyparview: a member with k takes one a neighbour shorttv4 days1-1/+4