mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-02-02 08:42:11 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update docs/about/faq.mdx

Browse source 
Co-authored-by: pdxlocations <117498748+pdxlocations@users.noreply.github.com>
This commit is contained in:
withoutgettingwet 2025-01-26 22:04:51 -06:00 committed by GitHub
parent 2d71e62b95
commit 19e5749e54
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/about/faq.mdx
View file

@ -172,9 +172,7 @@ If you use your ham radio license with Meshtastic, consider both the privileges
{
title: "Why aren’t licensed and unlicensed modes interoperable? Is this a planned feature?",
content: `
- Amateur radio regulations vary widely around the world; many countries have specific and often differing regulations against the use of encryption over amateur radio.
- Additionally, many countries have regulations preventing licensed operators from relaying third party messages (in this case, the messages of unlicensed stations) or the relaying of licensed stations’ messages without an accompanying call sign.
- This makes interoperability impossible at worst and unfeasible at best; as a result interoperability between these modes is not a planned feature.`,
Amateur radio regulations differ significantly across countries, with many prohibiting the use of encryption. Additionally, regulations in some countries restrict licensed operators from relaying messages from unlicensed stations or transmitting messages from licensed stations without including a call sign. These restrictions make interoperability highly impractical, if not impossible. Consequently, interoperability between these modes is not a planned feature.`,
},
],
"mesh": [