From 0bf4a52a764a637f03fc955508ce6e434f030007 Mon Sep 17 00:00:00 2001
From: anon <anon@nowhere.jez>
Date: Sat, 7 Jun 2025 16:14:06 +0200
Subject: [PATCH] fix index

---
 index.md               |  1 +
 simplexalerts/index.md | 50 ++++++++++++++++++++----------------------
 2 files changed, 25 insertions(+), 26 deletions(-)

diff --git a/index.md b/index.md
index 5eade1f..32e04bc 100644
--- a/index.md
+++ b/index.md
@@ -19,6 +19,7 @@ With this new mkdocs blog version, we have completely changed how you can find b
 (Check out [this blogpost](whytheblog/index.md) for more details on our mission)
 
 ## Our latest contributed tutorials:
+- 2025-06-07: [Anonymous Alerting System (via SimpleX)](simplexalerts/index.md)
 - 2025-06-07: [Stylometry Protection (Using Local LLMs) [old tutorial rewrite]](stylometry/index.md)
 - 2025-06-06: [Laws do not stop crimes](lawsdonotstopcrime/index.md)
 - 2025-06-05: [DoT, DoH, DNSCrypt, DNS over Tor and Local DNS: What actually protects you?](dnscrypt/index.md)
diff --git a/simplexalerts/index.md b/simplexalerts/index.md
index 81ed766..28828f0 100644
--- a/simplexalerts/index.md
+++ b/simplexalerts/index.md
@@ -7,10 +7,9 @@ tags:
   - Core Tutorial
 ---
 
-# The case for alerting
+# Anonymous Alerting System (via SimpleX)
 
-As you know, [monitoring](../anonymous_server_monitoring/index.md) is important when running any kind of operations, especially so
-for clandestine ones.
+As you know, [monitoring](../anonymous_server_monitoring/index.md) is important when running any kind of operations, especially so for clandestine ones.
 
 
 ## Alert Types
@@ -241,6 +240,7 @@ Run your client in server mode:
 
 This command will:
 - create two databases that your client uses for reconnecting to groups and interacting with the simpleX Network
+- make sure that simplex routes all traffic through Tor (thanks to the -x argument)
 - set this client display name (what you will see in your groups when receiving alerts)
 - open a websocket port that the alerter will use on 127.0.0.1:1337
 
@@ -502,9 +502,9 @@ And here's the alert:
 To turn the simplex-chat and the alerter into systemd services, you only need to create two files:
 
 ## /etc/systemd/system/simplex-chat.service
-```text
- vim /etc/systemd/system/simplex-chat.service
- cat /etc/systemd/system/simplex-chat.service
+```sh
+sudo vim /etc/systemd/system/simplex-chat.service
+sudo cat /etc/systemd/system/simplex-chat.service
 ```
 
     [Unit]
@@ -517,28 +517,26 @@ To turn the simplex-chat and the alerter into systemd services, you only need to
 
 ## /etc/systemd/system/alerter.service
 
-```text
-vim /etc/systemd/system/alerter.service
-cat /etc/systemd/system/xxx
+```sh
+sudo vim /etc/systemd/system/alerter.service
+sudo cat /etc/systemd/system/alerter.service
+
+[Unit]
+Requires=simplex-chat.service
+
+[Service]
+ExecStart=docker run --rm simplex-alerter -c /etc/alerter-config.yaml -e 127.0.0.1:1337
+
+[Install]
+WantedBy=simplex-chat.service
 ```
-
-
-    [Unit]
-    Requires=simplex-chat.service
-
-    [Service]
-    ExecStart=docker run --rm simplex-alerter -c /etc/alerter-config.yaml -e 127.0.0.1:1337
-
-    [Install]
-    WantedBy=simplex-chat.service
-
 ## Enable the services
-Now enable the services
-    
-    sudo systemctl daemon-reload
-    sudo systemctl enable --now simplex-chat.service
-    sudo systemctl enable --now alerter.service
-
+Now enable the service:
+```sh
+sudo systemctl daemon-reload
+sudo systemctl enable --now simplex-chat.service
+sudo systemctl enable --now alerter.service
+```
 # Conclusion
 
 We now have an easy way to set multiple alerts to different groups based on our monitoring system, furthermore those alerts will be sent over tor through a privacy-preserving messaging system.