aboutsummaryrefslogtreecommitdiffstats
Commit message (Expand)AuthorAgeFilesLines
* docs: remakes and signed valuestv2 days1-0/+3
* remake: a strict remake of a strict swarm isn't followedtv2 days3-1/+30
* roots: a joiner takes a root once its seeds named ittv2 days7-36/+134
* signatures: tell held changes as the screen doestv2 days1-4/+4
* screen: signatures required as the policy a change came under saystv2 days6-52/+98
* screen: share the heads a change is judged at with what it builds ontv2 days1-9/+19
* screen: move each change along instead of copying ittv2 days1-4/+4
* screen: order changes by their places, each hash looked up oncetv2 days1-36/+36
* screen: read once per batch whether the policy is stricttv2 days1-8/+29
* document: tell whether a document holds a change without building ittv2 days7-24/+60
* bench: break screening down after a long history tootv2 days1-7/+13
* access: read once what rules read at the same headstv2 days3-29/+136
* bench: break screening down per changetv2 days1-0/+103
* state: limit refused writes per usertv2 days10-1/+114
* roots: an epoch's root pinned, and named in every handshaketv2 days19-11/+336
* screen: what a node receives judged, policy or nottv2 days6-34/+59
* store: a write inside a list checked where the rules judge ittv2 days3-7/+78
* screen: changes put in order in one passtv2 days1-19/+37
* bench: what screening costs while catching uptv2 days2-2/+110
* strict: no strict remake of a swarm strict alreadytv2 days3-8/+21
* refusals: a big drop waits for a second member only where there is onetv2 days2-8/+17
* remake: aborts written as the user who asks; no abort by timetv2 days7-180/+69
* strict: a manifest serves one remake, at its basetv2 days5-18/+104
* remake: a strict remake makes the registry, policy and bans anewtv2 days2-0/+25
* docs: what a junk logout doestv2 days1-1/+5
* access: a change judged by the policy it was written under, locally tootv2 days2-2/+9
* screen: maps made, and votes, judged with what came before them intv2 days1-8/+30
* rules: under strict, a user's own entry is its own to signtv2 days1-0/+28
* remake: a replay taken back keeps the node its authortv2 days1-1/+72
* remake: no --follow-strict-remakes; a strict remake failing says whotv2 days12-45/+122
* remake: turning a running swarm strict, keeping what an operator signedtv3 days20-17/+740
* dashboard: a user's menu, with its credentials and logging outtv3 days2-20/+144
* users: a user can't remove its own last keytv3 days4-27/+112
* auth: no basic authentication offered to the dashboardtv3 days2-8/+12
* refusals: a drop taking much waits for a second member, and showstv3 days7-7/+108
* users: a user manages its own keystv3 days9-7/+286
* refusals: an import left unusedtv3 days1-1/+1
* login: logins by key capped per usertv3 days9-27/+148
* dashboard: log out of this browser, and say what can't betv3 days4-5/+48
* auth: no password prompt over the dashboard's own requeststv3 days2-5/+10
* simtest: forged changes, aborts of expired remakes, envelopes of another swarmtv3 days1-0/+185
* screen: waiting changes building on a refused one refused at oncetv3 days1-25/+90
* docs: a signed null keeps the prev chain goingtv3 days1-1/+4
* screen: a batch Automerge refuses names its changestv3 days1-2/+41
* future-work: decisions by their votes, where a token is handedtv3 days0-0/+0
* docs: what the review found that staystv3 days2-5/+22
* login: the session cookie Secure behind a TLS proxytv3 days2-2/+58
* dashboard: a content security policy, framed by nonetv3 days2-5/+59
* envelope: a signed value names its swarmtv3 days13-16/+52
* token: a banned node's tokens aren't takentv3 days3-6/+22