From c73e02635d5b044ee7fe3564e751aef5110d87c3 Mon Sep 17 00:00:00 2001
From: Chris Caron <lead2gold@gmail.com>
Date: Tue, 28 Dec 2021 11:55:42 -0500
Subject: [PATCH] Updated Notify_dapnet (markdown)

---
 Notify_dapnet.md | 41 +++++++++++++++++++++++++++++++++++++++--
 1 file changed, 39 insertions(+), 2 deletions(-)

diff --git a/Notify_dapnet.md b/Notify_dapnet.md
index 866d17e..c6d2c4d 100644
--- a/Notify_dapnet.md
+++ b/Notify_dapnet.md
@@ -19,12 +19,49 @@ Valid syntax's are as follows:
 | txgroups    | No       | The transmitter group(s) to associate with your message.  Use a comma (`,`) to identify more then one.  By default if this value isn't specified then the group `dl-all` is used.
 | batch       | No       | [Hampager](https://hampager.de) allows for a batch mode. If you identify more then one call sign, you can send all of them in a single shot instead of the normal Apprise approach (which sends them one by one). Enabling batch mode has both it's pro's and cons. By default batch mode is disabled.
 
-#### Example
+## Constraints
+
+* The DAPNET API permits you to specify more than one target call sign. Any unknown or invalid call sign in that list will [terminate the whole message broadcast for all call signs](https://hampager.de/dokuwiki/doku.php?id=dapnetapisendcall)
+* If the message exceeds 80 characters, the plugin will automatically truncate the content to DAPNET's max message length
+* If you specify an Apprise 'title' parameter, Apprise will automatically add that title to the message body along with a trailing ``\r\n`` control sequence which may result in undesired experiences. It is recommended to refrain from using Apprise's 'title' parameter.
+* For messages, it is recommended to stick to the English alphabet as DAPNET cannot process extended character sets like the cyrillic alphabet. The DAPNET API will still process messages with this content but the user's pager may not display them in a proper format.
+* In order to gain access to the DAPNET API, you need to be a licensed ham radio operator.
+
+### Example
+
+Send a DAPNET Notification :
+
+```bash
+# Assuming our {user} is df1abc
+# Assuming our {password} is appriseIsAwesome
+# Assuming our {callsign} - df1def
+#
+apprise -vv -b "Test Message Body" \
+   "dapnet://df1abc:appriseIsAwesome@df1def"
+
+# Assuming our {user} is df1abc
+# Assuming our {password} is appriseIsAwesome
+# Assuming our {callsign}s are - df1def,df1ghi and df1def-12
+# This will result in two target call signs as the plugin is going
+# to strip the '-12' ssid and detect the dupe call sign
+# 
+apprise -vv -b "Test Message Body" \
+   dapnet://df1abc:appriseIsAwesome@df1def/df1ghi/df1def-12
+
+# Assuming our {user} is df1abc
+# Assuming our {password} is test
+# Assuming our {callsign} - df1def
+# Assuming our {priority} - emergency
+# Assuming our {txgroups} - 'dl-all', 'all'
+apprise -vv -b "Test Message Body" \
+   "dapnet://df1abc:test@df1def?txgroups=dl-all,all&priority=emergency"
+```
+
 Send a DAPNET/Hampager notification to the callsign: `DF1ABC`
 ```bash
 # Assuming our {callsign} is DF1ABC
 # Assuming our {userid} is foobar
 # Assuming our {password} is pass123
 apprise -vv -b "Test Message Body" \
-   dapnet://foobar:pass123@DF1ABC
+   "dapnet://foobar:pass123@DF1ABC"
 ```