Repository navigation
Rakumux v0.1.26
Rakumux 0.1.26
Replies from rakumux.com arrive at once
- Signed in with the Agent feed on, the account service keeps a connection to rakumux.com and
reads your replies the moment you send one, instead of checking every few seconds. It still
checks once a minute in case a nudge is lost, and checks as before while the connection is down. - The connection carries nothing but "read now": your replies still come over the usual request.
Typed in once, and only into the agent
- A reply is typed in at most once. Before, the account service being replaced (by an update, for
one) while a reply waited to be reported could type it again. - A reply meant for an agent that has just quit stays at the shell's prompt instead of being run
there as a command. This needs the server restarted in place (below). - Each reply keeps its own answer: replies typed in one after another each get theirs, and one
whose turn ended without an answer (interrupted, an API error) no longer takes a later one. - Only replies written in this machine's TUI skip Settings → Replies from rakumux.com; before, a
reply from elsewhere could claim to be one.
Machines with the same name
- Each machine now keeps a name and an id of its own. Two machines with the same hostname, or two
Rakumux homes on one machine, no longer read each other's replies or replace each other's
sessions on rakumux.com: the second takes the name with a few characters after it. - A machine whose hostname changes keeps its name on rakumux.com, so replies to it still arrive.
Upgrading
U installs the update and reloads the UI; the account service is replaced by the new version by
itself. To keep replies out of a shell, restart the server in place too: press S in Rakumux
mode, then y (or run rakumux daemon restart). Your sessions keep running.