-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@jokeocracy@MorlockP@urbit_ ... so it won't be ready for public consumption until the root is immune to all forms of ill fortune?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@jokeocracy@MorlockP@urbit_ Okay, but it sounds odd. Maintaining continuity should be /easy/, and would /help/ with early development.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@jokeocracy@MorlockP@urbit_ Sorry for asking dumb questions, but I don't get why restarting a server means rebuilding all clients.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@john_burnham_
@jokeocracy@MorlockP What happens when ~doznec restarts that's different from ~doznec staying up? Why?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@john_burnham_
@jokeocracy@MorlockP@urbit_ Why are you recreating a network when one node restarts?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@john_burnham_
@jokeocracy@MorlockP ... and that event log is not persistent across restarts? Is that it?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@john_burnham_
@jokeocracy@MorlockP ... so a crash destroys some state, and the network is dependent on that node's state?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@john_burnham_
@random_eddie@jokeocracy think of nodes sharing one VAST event logging system, moving fwd in a shared state machine. >> -
@john_burnham_
@random_eddie@jokeocracy if state machine crashes why bother remembering that you were in state XYZ97? New scratch monkey >> - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.