From 9b3643e4aa0da1bb50c532850b9b614da7f9d51a Mon Sep 17 00:00:00 2001 From: ford-jones Date: Tue, 23 Sep 2025 11:46:10 +1200 Subject: [PATCH] Decouple node-mute from channel-mute --- meshtastic/admin.proto | 10 ---------- meshtastic/deviceonly.proto | 6 ------ 2 files changed, 16 deletions(-) diff --git a/meshtastic/admin.proto b/meshtastic/admin.proto index 2f805ca..0259c2a 100644 --- a/meshtastic/admin.proto +++ b/meshtastic/admin.proto @@ -414,16 +414,6 @@ message AdminMessage { */ uint32 remove_ignored_node = 48; - /* - * Set specified node-num to be muted - */ - uint32 set_muted_node = 49; - - /* - * Set specified node-num to be heard / not-muted - */ - uint32 remove_muted_node = 50; - /* * Begins an edit transaction for config, module config, owner, and channel settings changes * This will delay the standard *implicit* save to the file system and subsequent reboot behavior until committed (commit_edit_settings) diff --git a/meshtastic/deviceonly.proto b/meshtastic/deviceonly.proto index 7465399..ab439e3 100644 --- a/meshtastic/deviceonly.proto +++ b/meshtastic/deviceonly.proto @@ -159,12 +159,6 @@ message NodeInfoLite { */ bool is_ignored = 11; - /* - * True if node has been muted - * Persists between NodeDB internal clean ups - */ - bool is_muted = 12; - /* * Last byte of the node number of the node that should be used as the next hop to reach this node. */