-
Updated
Oct 8, 2020 - Go
xmpp
Here are 542 public repositories matching this topic...
-
Updated
Oct 4, 2020 - Go
-
Updated
Sep 25, 2020 - Objective-C
-
Updated
Oct 9, 2020 - Java
-
Updated
Oct 6, 2020 - Java
-
Updated
Jul 22, 2020 - Erlang
-
Updated
Oct 6, 2020 - JavaScript
It’d be useful for users to know which version they’re running on.
-
Updated
Jul 7, 2020 - Java
-
Updated
Sep 21, 2020 - JavaScript
-
Updated
Sep 10, 2020 - JavaScript
-
Updated
Oct 3, 2020 - PHP
-
Updated
May 3, 2020 - Java
-
Updated
Oct 6, 2020 - Go
-
Updated
Sep 30, 2020 - Objective-C
-
Updated
Oct 1, 2020 - TypeScript
For the feature Private key transfer #1090 you use Barcodes for verification.
Would it be a good idea to use the same way to verify Public key of contacts and mark this verificated users in contactlist with a green Icon or somewhat (similar to Threema )?
Maybe:
-yellow for "I'm not sure but I trust the key anyway and will verify it by our next beer."
-green for "I have scanned the code of m
-
Updated
Oct 9, 2020 - Java
Improve this page
Add a description, image, and links to the xmpp topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the xmpp topic, visit your repo's landing page and select "manage topics."
Describe the bug
Assume that one user is online with two clients at the same time. At least one of those clients is converse.js. The other client can also be converse, but could be any client that stores its bookmarks in PEP.
Now, change the bookmarks (add, change, or remove a bookmark) in the "other" client (not converse.js).
Expected behavior
One would expect that the bookmarks a