Updated messaging deck

2026-05-10 21:56:22 +02:00 · 2026-05-10 21:56:22 +02:00 · fa7fd32dcd
commit fa7fd32dcd
parent 6688ad0a59
1 changed files with 10 additions and 78 deletions
--- a/docs/møder/2026-05-11_messaging-presentation.md
+++ b/docs/møder/2026-05-11_messaging-presentation.md
@ -65,10 +65,12 @@ _All apps below support end-to-end encryption._
 Non-profit Signal Foundation. The Signal Protocol powers WhatsApp, Google RCS, and Messenger secret chats.

 **Pros**
+
 - Simplest UX — works like a normal messaging app
 - Audited, battle-tested cryptography; no ads, no tracking

 **Cons**
+
 - Phone number required — links identity to account
 - Centralized — Signal's servers, Signal's rules

@ -113,36 +115,26 @@ graph LR
 ## Matrix — Pros and Cons

 **Pros**
+
 - Fully open source, top to bottom
 - Self-host your server — you own your data
 - Federated — no single company controls the network
 - Bridges consolidate all your chats in one place

 **Cons**
+
 - E2EE key management is clunky (cross-signing, key backup)
 - Synapse is resource-hungry (~1 GB RAM)
 - The UX of Element is still maturing

 ---

-## Matrix — Why It's Interesting for MakerFLOSS
-
-We could run `matrix.makerfloss.eu` on our existing VPS.
-
- Full control over our community chat
- Bridges to reach people still on WhatsApp or Messenger
- A playground for self-hosted infrastructure
- Federated — members can also use matrix.org or personal servers
- ~500 MB RAM with Conduit (lighter than Synapse)
-
---
-
 ## Matrix Bridges — Stay Connected During the Transition

 A bridge relays messages between Matrix and another network — both ways.

 | Bridge                    | Network    | Notes                                      |
-| ------------------------- | ---------- | ------------------------------------------- |
+| ------------------------- | ---------- | ------------------------------------------ |
 | `mautrix-whatsapp`        | WhatsApp   | Puppeting — your real WA account           |
 | `mautrix-telegram`        | Telegram   | Puppeting — very stable                    |
 | `mautrix-signal`          | Signal     | Fragile — Signal actively breaks 3rd-party |
@ -172,63 +164,3 @@ Peer-to-peer messaging — _no server at all_.
 - Con: Android-first; no desktop client; both parties must be online to first connect

 **For:** activists, disaster scenarios, high-censorship environments
-
---
-
-## Participation — Let's Talk
-
-**Round 1: Your current situation** _(2 min, pairs)_
-
- What messenger do you use most, and why?
- Is there anything about it that bothers you?
-
-**Round 2: Barriers** _(group discussion)_
-
- What's the hardest part of switching or convincing others?
- "But all my friends are on WhatsApp" — how do you handle it?
-
---
-
-## Participation — Try It Now
-
-**Option A — Signal**
-Install Signal, register with your phone number, message the person next to you.
-
-**Option B — Matrix (web)**
-Open [app.element.io](https://app.element.io), create an account on matrix.org, join `#makerfloss:matrix.org`.
-
-**Option C — Discussion**
-Should MakerFLOSS run a Matrix homeserver?
-
---
-
-<!-- _class: invert dense -->
-
-## Resources
-
-| Resource                | Link                                                                                                    |
-| ----------------------- | ------------------------------------------------------------------------------------------------------- |
-| Signal                  | [signal.org](https://signal.org)                                                                        |
-| Element client          | [element.io](https://element.io)                                                                        |
-| Matrix spec             | [spec.matrix.org](https://spec.matrix.org)                                                              |
-| Conduit server          | [conduit.rs](https://conduit.rs)                                                                        |
-| Briar                   | [briarproject.org](https://briarproject.org)                                                            |
-| Privacy Guides          | [privacyguides.org/…/real-time-communication](https://www.privacyguides.org/en/real-time-communication) |
-| meshtastic-matrix-relay | [github: geoffwhittington/meshtastic-matrix-relay](https://github.com/geoffwhittington/meshtastic-matrix-relay) |
-
---
-
-## Summary
-
- **Signal**: easiest switch, best UX, E2EE by default — but centralized, requires phone number
- **Matrix**: most aligned with FLOSS values, self-hostable, federated — but more complex
- **XMPP**: the old guard, still solid for the technically inclined
- **Briar**: for extreme scenarios — no infrastructure needed
-
-**The best alternative is the one people will actually use.**
-
---
-
-# Questions?
-
-_Slides made with [Marp](https://marp.app) — open source markdown slide tool_