diff --git a/docs/posts/2026/encrypted_XMPP/index.html b/docs/posts/2026/encrypted_XMPP/index.html index 12f7e6b..dfa0355 100644 --- a/docs/posts/2026/encrypted_XMPP/index.html +++ b/docs/posts/2026/encrypted_XMPP/index.html @@ -149,7 +149,8 @@ is actually based on XMPP, but incompatibly altered and defederated. While the internal details are quite interesting, for practical purposes it’s enough to know that each client stores some cryptographic keys -and can derive a hash from them, commonly called a fingerprint.
+and can derive a human-readable hash from them, +commonly called a fingerprint.Keys are usually managed automatically by the XMPP client, and in normal use you should never need to handle them manually. In fact, you probably don’t even need to know what they look like.
@@ -408,14 +409,14 @@ when you keep running into “The message was not encrypted for this device” over and over again.From now on, I hope you won’t encounter such errors -or any other issues -connected to end-to-end encryption in XMPP.
+or any other issues with end-to-end encryption, +and you’ll feel confident using it in XMPP.