From e717816c6393d3a84cc73da4db09ec18b105ad73 Mon Sep 17 00:00:00 2001 From: n30nex Date: Wed, 1 Jul 2026 04:13:20 -0400 Subject: [PATCH 1/2] Update MQTT Data Collection & Access documentation Removed bad formatting on top line. --- docs/analyzer/data-collection-access.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/analyzer/data-collection-access.md b/docs/analyzer/data-collection-access.md index c876539..8a76fc4 100644 --- a/docs/analyzer/data-collection-access.md +++ b/docs/analyzer/data-collection-access.md @@ -1,7 +1,7 @@ # MQTT Data Collection & Access -!!! warning "Treat MeshCore RF traffic as public data" !!! - MeshCore traffic is intended for shared mesh use, and different networks may use different presets or frequencies (including non-default settings). All channels that use a shared public key (and private keys) should be considered inherently insecure. Any node transmitting MeshCore packets over matching settings can be heard by observers on that mesh, not just one published default profile. Traffic forwarded over MQTT through this path should be treated as potentially public. Do not transmit names, locations, notes, or other personal information unless you are comfortable with that information being stored and viewable publicly. Assume that even with encryption on a private channel / setting can potentially be collected and decrypted by anyone with the means and know-how to do so. + +MeshCore traffic is intended for shared mesh use, and different networks may use different presets or frequencies (including non-default settings). All channels that use a shared public key (and private keys) should be considered inherently insecure. Any node transmitting MeshCore packets over matching settings can be heard by observers on that mesh, not just one published default profile. Traffic forwarded over MQTT through this path should be treated as potentially public. Do not transmit names, locations, notes, or other personal information unless you are comfortable with that information being stored and viewable publicly. Assume that even with encryption on a private channel / setting can potentially be collected and decrypted by anyone with the means and know-how to do so. ## What We Collect From 594017a1fbab6148e53cb27f02fd67b125a5b97a Mon Sep 17 00:00:00 2001 From: n30nex Date: Wed, 1 Jul 2026 04:28:41 -0400 Subject: [PATCH 2/2] Restore MQTT data warning admonition --- docs/analyzer/data-collection-access.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/analyzer/data-collection-access.md b/docs/analyzer/data-collection-access.md index 8a76fc4..518d2e8 100644 --- a/docs/analyzer/data-collection-access.md +++ b/docs/analyzer/data-collection-access.md @@ -1,7 +1,7 @@ # MQTT Data Collection & Access - -MeshCore traffic is intended for shared mesh use, and different networks may use different presets or frequencies (including non-default settings). All channels that use a shared public key (and private keys) should be considered inherently insecure. Any node transmitting MeshCore packets over matching settings can be heard by observers on that mesh, not just one published default profile. Traffic forwarded over MQTT through this path should be treated as potentially public. Do not transmit names, locations, notes, or other personal information unless you are comfortable with that information being stored and viewable publicly. Assume that even with encryption on a private channel / setting can potentially be collected and decrypted by anyone with the means and know-how to do so. +!!! warning "Treat MeshCore RF traffic as public data" + MeshCore traffic is intended for shared mesh use, and different networks may use different presets or frequencies (including non-default settings). All channels that use a shared public key (and private keys) should be considered inherently insecure. Any node transmitting MeshCore packets over matching settings can be heard by observers on that mesh, not just one published default profile. Traffic forwarded over MQTT through this path should be treated as potentially public. Do not transmit names, locations, notes, or other personal information unless you are comfortable with that information being stored and viewable publicly. Assume that even with encryption on a private channel / setting can potentially be collected and decrypted by anyone with the means and know-how to do so. ## What We Collect