diff --git a/docs/møder/2026-05-xx-messaging-presentation.md b/docs/møder/2026-05-xx-messaging-presentation.md index 2ec5bbf..02964d9 100644 --- a/docs/møder/2026-05-xx-messaging-presentation.md +++ b/docs/møder/2026-05-xx-messaging-presentation.md @@ -8,7 +8,7 @@ paginate: true ### Free & Open Alternatives to WhatsApp and Messenger -MakerFLOSS · 2026 +MakerFLOSS · April 2026 --- @@ -20,38 +20,36 @@ Most people use WhatsApp, Messenger, or iMessage. - **WhatsApp** — owned by Meta; metadata harvested; backup encryption only added under pressure - **Messenger** — no E2EE by default in groups; extensive ad tracking -- **Telegram** — *not* E2EE by default; groups are server-side; closed server +- **Telegram** — _not_ E2EE by default; groups are server-side; closed server - **iMessage** — Apple lock-in; not available on Android or Linux -These apps are *convenient* — but the cost is your data and your network. +These apps are _convenient_ — but the cost is your data. --- -## What Would We Want Instead? +## Whish-list -| Property | Why it matters | -|---|---| -| End-to-end encryption | Only sender and recipient can read messages | -| Open source | Anyone can audit the code | -| Self-hostable | You control the server and the data | -| No phone number required | Less identity linkage | -| Cross-platform | Linux, Android, iOS, Windows | -| Federated / decentralized | No single point of failure or control | - -No single app checks every box — but the trade-offs are manageable. +| Property | Why it matters | +| ------------------------- | ------------------------------------------- | +| End-to-end encryption | Only sender and recipient can read messages | +| Open source | Anyone can audit the code | +| Self-hostable | You control the server and the data | +| No phone number required | Less identity linkage | +| Cross-platform | Linux, Android, iOS, Windows | +| Federated / decentralized | No single point of failure or control | --- ## The Landscape at a Glance -| App | E2EE | Open source | Self-host | No phone# | Federation | -|---|---|---|---|---|---| -| **Signal** | ✓ | Partial | ✗ | ✗ | ✗ | -| **Matrix / Element** | ✓ | ✓ | ✓ | ✓ | ✓ | -| **XMPP + OMEMO** | ✓ | ✓ | ✓ | ✓ | ✓ | -| **Briar** | ✓ | ✓ | N/A | ✓ | N/A | -| **Session** | ✓ | ✓ | Partial | ✓ | Partial | -| **Threema** | ✓ | ✓ | Partial | Optional | ✗ | +| App | E2EE | Open source | Self-host | No phone# | Federation | +| -------------------- | ---- | ----------- | --------- | --------- | ---------- | +| **Signal** | ✓ | Partial | ✗ | ✗ | ✗ | +| **Matrix / Element** | ✓ | ✓ | ✓ | ✓ | ✓ | +| **XMPP + OMEMO** | ✓ | ✓ | ✓ | ✓ | ✓ | +| **Briar** | ✓ | ✓ | N/A | ✓ | N/A | +| **Session** | ✓ | ✓ | Partial | ✓ | Partial | +| **Threema** | ✓ | ✓ | Partial | Optional | ✗ | --- @@ -63,12 +61,14 @@ No single app checks every box — but the trade-offs are manageable. WhatsApp, Google Messages (RCS), Skype, Facebook Messenger (secret chats) ### Pros + - Extremely simple UX — works like a normal messaging app - Calls, groups, disappearing messages, Stories, Note to Self - Audited, battle-tested cryptography - No ads, no tracking, no data sold ### Cons + - Phone number required — links your identity to your account - Centralized — Signal's servers, Signal's rules - Server source code published but community forks are blocked @@ -83,7 +83,7 @@ Alice's phone Signal Server Bob's phone [message] ──encrypt(Bob's key)──▶ [stores ciphertext] ──────▶ decrypt ──▶ [message] ``` -- The server sees: *who* talks to *whom*, *when*, and *how often* +- The server sees: _who_ talks to _whom_, _when_, and _how often_ - The server does **not** see: message content - This metadata is still significant — [read the Signal subpoena responses](https://signal.org/bigbrother/) @@ -111,6 +111,7 @@ Matrix is a **protocol**, not an app — like email, but for real-time chat. ## Matrix — Pros and Cons ### Pros + - Fully open source, top to bottom - Self-host your own homeserver — you own your data - Federated — no single company controls the network @@ -118,6 +119,7 @@ Matrix is a **protocol**, not an app — like email, but for real-time chat. - Persistent rooms, Spaces (like Discord servers), threads ### Cons + - E2EE key management is still clunky (cross-signing, key backup) - Synapse is resource-hungry (~1 GB RAM for a small server) - Message history sync across federation is slow @@ -130,12 +132,14 @@ Matrix is a **protocol**, not an app — like email, but for real-time chat. We could run our own homeserver at `matrix.makerfloss.eu`. **What this gives us:** + - Full control over our community chat - Bridges to reach people still on WhatsApp or Messenger - A playground for learning about self-hosted infrastructure - Federated — members can also use matrix.org or their personal servers **Resources needed:** + - A VPS (we already have one at `88.99.32.236`) - ~500 MB RAM for Conduit (lighter than Synapse) - A subdomain + TLS (Traefik already handles this) @@ -145,14 +149,18 @@ We could run our own homeserver at `matrix.makerfloss.eu`. ## Two More Worth Knowing ### XMPP (Jabber) -The *original* federated chat standard — 1999. Still alive and kicking. + +The _original_ federated chat standard — 1999. Still alive and kicking. + - Extremely mature and lightweight - Good clients: **Conversations** (Android), **Monal** (iOS/macOS), **Gajim** (desktop) - E2EE via OMEMO - Con: fragmented client quality; setup less beginner-friendly ### Briar -Peer-to-peer messaging — *no server at all*. + +Peer-to-peer messaging — _no server at all_. + - Works over Tor, local WiFi, or Bluetooth (offline!) - Censorship-resistant by design - Con: Android only (iOS in beta); no desktop client; both parties must be online to first connect @@ -161,12 +169,12 @@ Peer-to-peer messaging — *no server at all*. ## Participation — Let's Talk -**Round 1: Your current situation** *(2 min, pairs)* +**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)* +**Round 2: Barriers** _(group discussion)_ - What's the hardest part of switching or convincing others to switch? - "But all my friends are on WhatsApp" — how do you handle it? @@ -175,14 +183,16 @@ Peer-to-peer messaging — *no server at all*. ## Participation — Hands-On Options -Pick one to try *right now*: +Pick one to try _right now_: **Option A — Signal** + 1. Install Signal on your phone 2. Register with your phone number 3. Send a message to the person next to you **Option B — Matrix (web)** + 1. Open [app.element.io](https://app.element.io) in your browser 2. Create a free account on matrix.org 3. Join the room `#makerfloss:matrix.org` (if it exists — let's create it!) @@ -194,16 +204,16 @@ Should MakerFLOSS set up a Matrix homeserver? What would it take? ## Resources -| Resource | Link | -|---|---| -| Signal | signal.org | -| Matrix spec | spec.matrix.org | -| Element client | element.io | -| FluffyChat | fluffychat.im | -| Conduit server | conduit.rs | -| Briar | briarproject.org | -| Privacy Guides (comparison) | privacyguides.org/en/real-time-communication | -| EFF Surveillance Self-Defense | ssd.eff.org | +| Resource | Link | +| ----------------------------- | -------------------------------------------- | +| Signal | signal.org | +| Matrix spec | spec.matrix.org | +| Element client | element.io | +| FluffyChat | fluffychat.im | +| Conduit server | conduit.rs | +| Briar | briarproject.org | +| Privacy Guides (comparison) | privacyguides.org/en/real-time-communication | +| EFF Surveillance Self-Defense | ssd.eff.org | --- @@ -220,4 +230,4 @@ Should MakerFLOSS set up a Matrix homeserver? What would it take? # Questions? -*Slides made with [Marp](https://marp.app) — open source markdown slide tool* +_Slides made with [Marp](https://marp.app) — open source markdown slide tool_ diff --git a/docs/test-slide.md b/docs/test-slide.md index dd0c81a..b922eea 100644 --- a/docs/test-slide.md +++ b/docs/test-slide.md @@ -1,4 +1,5 @@ --- +marp: true theme: gaia _class: lead paginate: true