From 573d8ea1e235acc982391897acd1de7e9f9256af Mon Sep 17 00:00:00 2001 From: redoomed1 Date: Thu, 20 Mar 2025 19:04:00 -0700 Subject: [PATCH] style: Format hyperlink Signed-off-by: redoomed1 --- docs/real-time-communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/real-time-communication.md b/docs/real-time-communication.md index e9c9cc1c..9ef29f37 100644 --- a/docs/real-time-communication.md +++ b/docs/real-time-communication.md @@ -285,4 +285,4 @@ Our best-case criteria represents what we would like to see from the perfect pro [^1]: [Forward secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) is where keys are rotated very frequently, so that if the current encryption key is compromised, it does not expose **past** messages as well. [^2]: Future Secrecy (or Post-Compromise Security) is a feature where an attacker is prevented from decrypting **future** messages after compromising a private key, unless they compromise more session keys in the future as well. This effectively forces the attacker to intercept all communication between parties, since they lose access as soon as a key exchange occurs that is not intercepted. -[^3]: You may refer to this step-by-step tutorial in German on how to set up UnifiedPush as the notification provider for Molly: https://kuketz-blog.de/messenger-wechsel-von-signal-zu-molly-unifiedpush-mollysocket-ntfy. +[^3]: You may refer to this step-by-step tutorial in German on how to set up UnifiedPush as the notification provider for Molly: [https://kuketz-blog.de/messenger-wechsel-von-signal-zu-molly-unifiedpush-mollysocket-ntfy](https://kuketz-blog.de/messenger-wechsel-von-signal-zu-molly-unifiedpush-mollysocket-ntfy).