aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Expand)AuthorAgeFilesLines
...
* dashboard: a subscribed node's message written out, read from it when showntv9 days4-15/+70
* dashboard: the transport each message went by, in the consoletv9 days4-35/+87
* access: what a node holds alone by `_continuum/local/<node ID>/<name>`tv10 days4-27/+76
* access: `*` for any one key in a capability's pathtv10 days4-33/+68
* paths: PINGs of a path take turns with the peer'stv10 days1-4/+82
* api: a log line per HTTP requesttv10 days3-5/+67
* remake: earlier epochs' metadata read as the snapshot built ittv10 days2-9/+55
* dashboard: the replay window and archive retention in the remake dialogtv10 days1-0/+32
* remake: replayWindow and archiveRetention in an octet-stream import's querytv10 days1-2/+50
* remake: leave out earlier epochs' metadata past the replay windowtv10 days2-5/+123
* access: keep an SSH key's commenttv10 days3-4/+23
* dashboard: no subscription to this node itselftv10 days1-1/+8
* dashboard: keys edited, the last removed with a password, failures kepttv10 days5-85/+211
* dashboard: a node's menu on a right-click, and going to its dashboardtv10 days1-5/+14
* dashboard: move pull slider to link legendtv10 days1-29/+43
* dashboard: an entry's menu left of the fingertv10 days1-4/+12
* dashboard: the document box edited from its menus alonetv10 days1-45/+19
* dashboard: an entry's menu in the document boxtv10 days1-25/+192
* dashboard: where a stream's lag comes fromtv10 days2-25/+63
* dashboard: the console in the order messages wenttv10 days1-4/+20
* dashboard: messages on one timeline, when they wenttv10 days1-28/+120
* dashboard: messages as they cometv10 days3-105/+143
* dashboard: messages run as they left; a link breathes red for those losttv10 days1-11/+126
* dashboard: messages follow the line they went overtv10 days1-27/+68
* dashboard: how hard links pull, on a dynamic maptv10 days1-2/+26
* dashboard: no dotted links for an end the page doesn't readtv10 days1-11/+7
* dashboard: every kind of message coloured and in the legendtv10 days1-4/+8
* changes: Context where it is usedtv10 days1-1/+2
* screen: what apply_bytes did, without how many it appliedtv10 days1-3/+0
* sync: a message carries the signatures of its changestv10 days4-63/+57
* sync: a test exchanging until level, not one answertv10 days1-0/+17
* sync: signatures sent again after a failed sendtv10 days1-6/+16
* swarm: no SIGNATUREStv10 days10-167/+11
* sync: signatures go with changes onlytv10 days2-2/+19
* signatures: sign what is senttv10 days6-75/+55
* signatures: a node signs at start what it kept unsigned when it stoppedtv10 days2-0/+60
* roots: a peer contradicting --genesis-root refused at the handshaketv10 days1-2/+18
* state: refused writes limited for the node tootv10 days2-17/+53
* screen: judged after the policy is gone, tootv10 days3-6/+64
* remake: a strict remake of a strict swarm isn't followedtv10 days2-0/+28
* roots: a joiner takes a root once its seeds named ittv10 days5-32/+128
* signatures: tell held changes as the screen doestv10 days1-4/+4
* screen: signatures required as the policy a change came under saystv10 days5-51/+96
* screen: share the heads a change is judged at with what it builds ontv10 days1-9/+19
* screen: move each change along instead of copying ittv10 days1-4/+4
* screen: order changes by their places, each hash looked up oncetv10 days1-36/+36
* screen: read once per batch whether the policy is stricttv10 days1-8/+29
* document: tell whether a document holds a change without building ittv10 days7-24/+60
* bench: break screening down after a long history tootv10 days1-7/+13
* access: read once what rules read at the same headstv10 days3-29/+136