4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c161521e49	dunst: keep what is shown once out of the history, and say whether notifications are paused ... The review of 2026-10-09 (H4): a link's code shown on the desk stayed in dunst's history, which node-notifier.history serves to every caller of the mesh's verbs, agents among them; and a code sent to a paused notifier is held and shown later, to whoever is then at the screen. send now takes secret (transient, category mesh.secret) and transient; the dunstrc's rules keep both out of the history, and history leaves out any that got there. The pause, read from dunst itself, is said as the event paused at start, on change and every two minutes, for the desk to read.	2026-10-09 17:08:17 +02:00
jochen	d83711f11e	Take only acknowledgements from a desk click, and make each answer a one-time ticket ... Review found that any process of the operator's account can choose a dunst action, so a click could release or stop a delivery in the operator's name; that tokens lived for ever; that a warning's answers died in ten seconds; and that a restarted notifier left dead buttons (hq ADR 0258).	2026-10-08 14:38:24 +02:00
jochen	f00b5a19b1	Say what the operator needs to do, keep quiet what needs nothing, and take answers from the desk ... The operator could not tell from a notification whether to act, nor act without opening a session. Each message now opens with a verdict, a warning that needs nothing is not sent, and a notification offers answers the messenger performs through their seat verbs; dunst's send gains actions and says the chosen one (hq ADR 0253).	2026-10-08 13:57:33 +02:00
jochen	8bbea4a2ad	dunst: the notifier as a module, claiming node-notifier and serving send and history (hq ADR 0208) ... Owns one dunstrc (the laptop's, in the interface face, its menu on the seat's dmenu command) and the dunstrc.d directory for other modules' rules; D-Bus starts it, so nothing else does. Go tools over the session bus.	2026-10-04 13:15:39 +02:00