Files
mesh-catalog/modules/desk-channel

desk-channel

The desk as a channel of the operator's conversation: kind desktop of the channel and intake benches the router (messenger) declares (novox/hq ADR 0258, ADR 0259). It shows the router's messages on the notifier of each machine the operator sits at (the node-notifier seat), and says which button was chosen there.

  • It proves nothing about who clicked. Any process of the operator's account can choose a notification's action (dunstctl action), so its claim declares no verified-sender: the router offers here only acknowledgements (Silence for a week, Details) and says in the words where an approval can be given.
  • An answer is taken only on a machine its message was shown on, and once; a refused click is said where it was made. A message with buttons stays until it is dismissed.
  • A notifier that started again (dunst.started) is shown again every open message with buttons it showed.
  • A message no machine took is said to the router as failed; the router tries it again.

What the operator gives

The machines to show on, as a setting: settings for desk-channel with {"desktop-machines": ["<the machine the operator sits at>", …]}. Until then it says it cannot send, and the router sends warnings to the channel that reaches the operator away.

Where it runs

Held once for the mesh, on the same machine as the router, which is where it is assigned. A message the router marks secret (a link's code) is shown and kept nowhere of this module's; the desktop's own notifier history may still hold it for its length (20 notifications). It asks each machine's notifier through the mesh: nothing new runs on the machines.

Tools

tool does
desk_channel_status whether it can show messages, the machines and each one's last answer, and its rules