Clarify non-private messaging (#56)

* Clarify non-private messaging

Clarify that directed messages are not guaranteed to be private since 
anyone can view the arednmesh message repository.

* Clarify non-private messaging

Fix typo in screenshot.
This commit is contained in:
Steve Lewis KC0EUW 2020-04-09 10:02:40 -07:00 committed by GitHub
parent e1e2586b5b
commit 7c12e4e559
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 1 additions and 2 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 34 KiB

View File

@ -48,13 +48,12 @@ The :abbr:`OLSR (Optimized Link State Routing protocol)` **Entries** show the to
Node and Broadcast Messages
---------------------------
The AREDN |trade| development team now has the ability to post messages which Internet-connected nodes will automatically retrieve once every 12 hours. There are two types of messages: QST/broadcast messages intended for all nodes, and directed messages which are only retrieved by individual nodes. Messages are displayed at the top of the *Node Status* page above the node name.
The AREDN |trade| development team now has the ability to post messages which Internet-connected nodes will automatically retrieve once every 12 hours. There are two types of messages: QST/broadcast messages intended for all nodes, and directed messages which are only retrieved by individual nodes. Messages are displayed at the top of the *Node Status* page above the node name. Be aware that there is no guarantee of privacy for these messages, since anyone can view the message repository online.
.. image:: _images/node-messages.png
:alt: Node Message Display
:align: center
Signal Charts
-------------