Update manpage.

go.mod

@@ -2,6 +2,7 @@ module salsa.debian.org/mdosch/go-sendxmpp
 
 go 1.17
 
+replace github.com/mattn/go-xmpp => /home/martin/build/go-xmpp
 require (
 	github.com/ProtonMail/gopenpgp/v2 v2.4.8
 	github.com/beevik/etree v1.1.0

man/go-sendxmpp.1

@@ -1,6 +1,6 @@
 .\" generated with Ronn-NG/v0.9.1
 .\" http://github.com/apjanke/ronn-ng/tree/0.9.1
-.TH "GO\-SENDXMPP" "1" "May 2022" ""
+.TH "GO\-SENDXMPP" "1" "July 2022" ""
 .SH "NAME"
 \fBgo\-sendxmpp\fR \- A little tool to send messages to an XMPP contact or MUC\.
 .SH "SYNOPSIS"
@@ -34,7 +34,7 @@ You can either pipe a programs output to \fBgo\-sendxmpp\fR, write in your termi
 .P
 \fB\-\-ox\fR: Use "OpenPGP for XMPP" encryption (experimental)\.
 .br
-\fBOx\fR in go\-sendxmpp only supports sending encrypted 1\-1 messages\. Sending to groupchats and sending encrypted files is not supported\. There is no check whether the recipients key is trusted as there is no local keyring used\. Go\-sendxmpp just uses the most recent key that is provided via pubsub and checks that it is not expired\.
+Ox in go\-sendxmpp only supports sending encrypted 1\-1 messages\. Sending to groupchats and sending encrypted files is not supported\. There is no check whether the recipients key is trusted as there is no local keyring used\. Go\-sendxmpp just uses the most recent key that is provided via pubsub and checks that it is not expired\. As a user facing client a notification would be shown that a new key is available and ask the user whether to use the new key or stick to the old one\. As go\-sendxmpp is usually used in scripts it just accepts the new key to prevent the user from missing a new notification due to changed keys\.
 .P
 \fB\-\-ox\-delete\-nodes\fR: Delete existing OpenPGP nodes on the server\.
 .P
@@ -54,7 +54,7 @@ If there is an existing private key for "OpenPGP for XMPP" created by another cl
 .P
 \fB\-p\fR, \fB\-\-password\fR=[\fIvalue\fR]: Password for XMPP account\.
 .P
-\fB\-\-raw\fR: Send raw XML\. To send raw XML to a contact as normal chat message no contact must be specified\. To send raw XML to a MUC you have to specify the MUC via \fB\-c\fR and \fBgo\-sendxmpp\fR will join the MUC\.
+\fB\-\-raw\fR: Send raw XML\. To send raw XML to a contact as normal chat message no contact must be specified\. To send raw XML to a MUC you have to specify the MUC via \fB\-c\fR and go\-sendxmpp will join the MUC\.
 .P
 \fB\-r\fR, \fB\-\-resource\fR=[\fIvalue\fR]: Set resource\. When sending to a chatroom this is used as 'alias'\.
 .P

man/go-sendxmpp.1.html

@@ -127,11 +127,14 @@ file location is specified with <code>-f</code> or <code>--file</code>.</p>
 
 <p><code>--ox</code>:
   Use "OpenPGP for XMPP" encryption (experimental).  <br>
-  <code>Ox</code> in go-sendxmpp only supports sending encrypted 1-1 messages. Sending to groupchats and
+  Ox in go-sendxmpp only supports sending encrypted 1-1 messages. Sending to groupchats and
   sending encrypted files is not supported.
   There is no check whether the recipients key is trusted as there is no local keyring used.
   Go-sendxmpp just uses the most recent key that is provided via pubsub and checks that it is not
-  expired.</p>
+  expired. As a user facing client a notification would be shown that a new key is available and
+  ask the user whether to use the new key or stick to the old one. As go-sendxmpp is usually
+  used in scripts it just accepts the new key to prevent the user from missing a new notification
+  due to changed keys.</p>
 
 <p><code>--ox-delete-nodes</code>:
   Delete existing OpenPGP nodes on the server.</p>
@@ -168,7 +171,7 @@ file location is specified with <code>-f</code> or <code>--file</code>.</p>
 
 <p><code>--raw</code>:
   Send raw XML. To send raw XML to a contact as normal chat message no contact must be specified.
-  To send raw XML to a MUC you have to specify the MUC via <code>-c</code> and <code>go-sendxmpp</code> will join the MUC.</p>
+  To send raw XML to a MUC you have to specify the MUC via <code>-c</code> and go-sendxmpp will join the MUC.</p>
 
 <p><code>-r</code>, <code>--resource</code>=[<var>value</var>]:
   Set resource. When sending to a chatroom this is used as 'alias'.</p>
@@ -207,7 +210,7 @@ License: BSD 2-clause License</p>
 
   <ol class='man-decor man-foot man foot'>
     <li class='tl'></li>
-    <li class='tc'>May 2022</li>
+    <li class='tc'>July 2022</li>
     <li class='tr'>go-sendxmpp(1)</li>
   </ol>
 

man/go-sendxmpp.1.ronn

@@ -52,11 +52,14 @@ file location is specified with `-f` or `--file`.
 
   `--ox`:
   Use "OpenPGP for XMPP" encryption (experimental).    
-  `Ox` in go-sendxmpp only supports sending encrypted 1-1 messages. Sending to groupchats and
+  Ox in go-sendxmpp only supports sending encrypted 1-1 messages. Sending to groupchats and
   sending encrypted files is not supported.
   There is no check whether the recipients key is trusted as there is no local keyring used.
   Go-sendxmpp just uses the most recent key that is provided via pubsub and checks that it is not
-  expired.
+  expired. As a user facing client a notification would be shown that a new key is available and
+  ask the user whether to use the new key or stick to the old one. As go-sendxmpp is usually
+  used in scripts it just accepts the new key to prevent the user from missing a new notification
+  due to changed keys.
 
   `--ox-delete-nodes`:
   Delete existing OpenPGP nodes on the server.
@@ -93,7 +96,7 @@ file location is specified with `-f` or `--file`.
 
   `--raw`:
   Send raw XML. To send raw XML to a contact as normal chat message no contact must be specified.
-  To send raw XML to a MUC you have to specify the MUC via `-c` and `go-sendxmpp` will join the MUC.
+  To send raw XML to a MUC you have to specify the MUC via `-c` and go-sendxmpp will join the MUC.
 
   `-r`, `--resource`=[<value>]:
   Set resource. When sending to a chatroom this is used as 'alias'.