presentation: trim all slides to fit one screen
- Max ~8 content lines per slide, tables max 5-7 rows - Split Signal pros/cons to use bold instead of ### subheadings - Split "Two More Worth Knowing" into separate XMPP and Briar slides - Trim bridges table (drop duplicate IRC row) - Trim resources table to 7 essential links - Tighten participation slides Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
sjat
parent
72eee63651
commit
888a28a947
1 changed files with 104 additions and 87 deletions
|
|
@ -9,7 +9,7 @@ paginate: true
|
||||||
|
|
||||||
### Free & Open Alternatives to WhatsApp and Messenger
|
### Free & Open Alternatives to WhatsApp and Messenger
|
||||||
|
|
||||||
MakerFLOSS · April 2026
|
MakerFLOSS · May 2026
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -17,18 +17,16 @@ MakerFLOSS · April 2026
|
||||||
|
|
||||||
Most people use WhatsApp, Messenger, or iMessage.
|
Most people use WhatsApp, Messenger, or iMessage.
|
||||||
|
|
||||||
**What's the problem?**
|
- **WhatsApp** — owned by Meta; metadata harvested
|
||||||
|
- **Messenger** — no E2EE by default in groups; ad tracking
|
||||||
- **WhatsApp** — owned by Meta; metadata harvested; backup encryption only added under pressure
|
- **Telegram** — _not_ E2EE by default; closed server
|
||||||
- **Messenger** — no E2EE by default in groups; extensive ad tracking
|
- **iMessage** — Apple lock-in; no Android or Linux
|
||||||
- **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.
|
These apps are _convenient_ — but the cost is your data.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Whish-list
|
## Wish-list
|
||||||
|
|
||||||
| Property | Why it matters |
|
| Property | Why it matters |
|
||||||
| ------------------------- | ------------------------------------------- |
|
| ------------------------- | ------------------------------------------- |
|
||||||
|
|
@ -50,51 +48,42 @@ These apps are _convenient_ — but the cost is your data.
|
||||||
| **XMPP + OMEMO** | ✓ | ✓ | ✓ | ✓ | ✓ |
|
| **XMPP + OMEMO** | ✓ | ✓ | ✓ | ✓ | ✓ |
|
||||||
| **Briar** | ✓ | ✓ | N/A | ✓ | N/A |
|
| **Briar** | ✓ | ✓ | N/A | ✓ | N/A |
|
||||||
| **Session** | ✓ | ✓ | Partial | ✓ | Partial |
|
| **Session** | ✓ | ✓ | Partial | ✓ | Partial |
|
||||||
| **Threema** | ✓ | ✓ | Partial | Optional | ✗ |
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Signal — The Gold Standard for E2EE
|
## Signal — The Gold Standard for E2EE
|
||||||
|
|
||||||
**Created by** Moxie Marlinspike (2013), now run by the non-profit Signal Foundation.
|
Non-profit Signal Foundation. The Signal Protocol powers WhatsApp, Google RCS, and Messenger secret chats.
|
||||||
|
|
||||||
**The Signal Protocol** is the encryption layer also used by:
|
**Pros**
|
||||||
WhatsApp, Google Messages (RCS), Skype, Facebook Messenger (secret chats)
|
- Simplest UX — works like a normal messaging app
|
||||||
|
- Audited, battle-tested cryptography; no ads, no tracking
|
||||||
|
|
||||||
### Pros
|
**Cons**
|
||||||
|
- Phone number required — links identity to account
|
||||||
- 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
|
- Centralized — Signal's servers, Signal's rules
|
||||||
- Server source code published but community forks are blocked
|
|
||||||
|
**Best for:** journalists, activists, everyday secure messaging
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Signal — Under the Hood
|
## Signal — Under the Hood
|
||||||
|
|
||||||
```
|
```
|
||||||
Alice's phone Signal Server Bob's phone
|
Alice's phone Signal Server Bob's phone
|
||||||
───────────── ───────────── ──────────
|
───────────── ───────────── ──────────
|
||||||
[message] ──encrypt(Bob's key)──▶ [stores ciphertext] ──────▶ decrypt ──▶ [message]
|
[message] ──encrypt(Bob)───▶ [stores ciphertext] ──────▶ decrypt ──▶ [message]
|
||||||
```
|
```
|
||||||
|
|
||||||
- The server sees: _who_ talks to _whom_, _when_, and _how often_
|
- Server sees: _who_ talks to _whom_, _when_, _how often_
|
||||||
- The server does **not** see: message content
|
- Server does **not** see: message content
|
||||||
- This metadata is still significant — [read the Signal subpoena responses](https://signal.org/bigbrother/)
|
- Metadata still matters — [Signal subpoena responses](https://signal.org/bigbrother/)
|
||||||
|
|
||||||
**Best for:** journalists, activists, family group chats, anyone who wants simple + secure
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Matrix — The Federated Open Standard
|
## Matrix — The Federated Open Standard
|
||||||
|
|
||||||
Matrix is a **protocol**, not an app — like email, but for real-time chat.
|
Matrix is a **protocol**, not an app — like email for real-time chat.
|
||||||
|
|
||||||
```
|
```
|
||||||
[your homeserver] ←──federation──▶ [another homeserver]
|
[your homeserver] ←──federation──▶ [another homeserver]
|
||||||
|
|
@ -102,101 +91,129 @@ Matrix is a **protocol**, not an app — like email, but for real-time chat.
|
||||||
Element client FluffyChat client
|
Element client FluffyChat client
|
||||||
```
|
```
|
||||||
|
|
||||||
- **Standard**: matrix.org (open spec, anyone can implement)
|
- **Servers**: Synapse (Python), Conduit (Rust), Dendrite (Go)
|
||||||
- **Server software**: Synapse (Python), Conduit (Rust), Dendrite (Go)
|
- **Clients**: Element, FluffyChat, Cinny, Fractal, Nheko
|
||||||
- **Clients**: Element, FluffyChat, Cinny, Fractal (GNOME), Nheko
|
- **Bridges**: WhatsApp, Telegram, Signal, IRC, Discord…
|
||||||
- **Bridges**: WhatsApp, Signal, Slack, Discord, IRC, XMPP — all bridgeable
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Matrix — Pros and Cons
|
## Matrix — Pros and Cons
|
||||||
|
|
||||||
### Pros
|
**Pros**
|
||||||
|
|
||||||
- Fully open source, top to bottom
|
- Fully open source, top to bottom
|
||||||
- Self-host your own homeserver — you own your data
|
- Self-host your server — you own your data
|
||||||
- Federated — no single company controls the network
|
- Federated — no single company controls the network
|
||||||
- Bridges let you consolidate all your chats in one place
|
- Bridges consolidate all your chats in one place
|
||||||
- Persistent rooms, Spaces (like Discord servers), threads
|
|
||||||
|
|
||||||
### Cons
|
**Cons**
|
||||||
|
- E2EE key management is clunky (cross-signing, key backup)
|
||||||
- E2EE key management is still clunky (cross-signing, key backup)
|
- Synapse is resource-hungry (~1 GB RAM)
|
||||||
- Synapse is resource-hungry (~1 GB RAM for a small server)
|
|
||||||
- Message history sync across federation is slow
|
|
||||||
- The UX of Element is still maturing
|
- The UX of Element is still maturing
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Matrix — Why It's Interesting for MakerFLOSS
|
## Matrix — Why It's Interesting for MakerFLOSS
|
||||||
|
|
||||||
We could run our own homeserver at `matrix.makerfloss.eu`.
|
We could run `matrix.makerfloss.eu` on our existing VPS.
|
||||||
|
|
||||||
**What this gives us:**
|
|
||||||
|
|
||||||
- Full control over our community chat
|
- Full control over our community chat
|
||||||
- Bridges to reach people still on WhatsApp or Messenger
|
- Bridges to reach people still on WhatsApp or Messenger
|
||||||
- A playground for learning about self-hosted infrastructure
|
- A playground for self-hosted infrastructure
|
||||||
- Federated — members can also use matrix.org or their personal servers
|
- 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
|
## Matrix Bridges — Stay Connected During the Transition
|
||||||
|
|
||||||
A bridge connects Matrix to another network — messages flow both ways.
|
A bridge relays messages between Matrix and another network — both ways.
|
||||||
|
|
||||||
```
|
| Bridge | Network | Notes |
|
||||||
[WhatsApp contact] ←──── WhatsApp servers ────▶ [mautrix-whatsapp bridge] ←──── Matrix ────▶ [You]
|
| ------------------------- | ---------- | ------------------------------------------- |
|
||||||
```
|
| `mautrix-whatsapp` | WhatsApp | Puppeting — your real WA account |
|
||||||
|
| `mautrix-telegram` | Telegram | Puppeting — very stable |
|
||||||
|
| `mautrix-signal` | Signal | Fragile — Signal actively breaks 3rd-party |
|
||||||
|
| `meshtastic-matrix-relay` | Meshtastic | LoRa mesh ↔ Matrix — off-grid messaging |
|
||||||
|
|
||||||
**You keep your existing accounts. Your contacts don't need to switch.**
|
**Catch:** Puppeting bridges hold your credentials. WhatsApp's ToS prohibits it — occasional bans occur.
|
||||||
|
|
||||||
| Bridge | Network | Notes |
|
|
||||||
| ----------------------- | -------- | ------------------------------------------ |
|
|
||||||
| `mautrix-whatsapp` | WhatsApp | Puppeting — uses your real WA account |
|
|
||||||
| `mautrix-telegram` | Telegram | Puppeting — very stable |
|
|
||||||
| `mautrix-signal` | Signal | Fragile — Signal actively breaks 3rd-party |
|
|
||||||
| `matrix-appservice-irc` | IRC | Mature, widely used |
|
|
||||||
| `heisenbridge` | IRC | Simpler alternative |
|
|
||||||
| `meshtastic-matrix-relay` | MeshCore / Meshtastic | LoRa mesh ↔ Matrix — off-grid messaging |
|
|
||||||
|
|
||||||
**The pitch:** Use Matrix as your single inbox — WhatsApp, Telegram, IRC all in one place.
|
|
||||||
|
|
||||||
**The catch:** Puppeting bridges need server access to your account credentials. WhatsApp's ToS prohibits it — occasional bans occur.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Two More Worth Knowing
|
## XMPP (Jabber)
|
||||||
|
|
||||||
### 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
|
- Extremely mature and lightweight
|
||||||
- Good clients: **Conversations** (Android), **Monal** (iOS/macOS), **Gajim** (desktop)
|
|
||||||
- E2EE via OMEMO
|
- E2EE via OMEMO
|
||||||
- Con: fragmented client quality; setup less beginner-friendly
|
- Good clients: **Conversations** (Android), **Monal** (iOS/macOS), **Gajim** (desktop)
|
||||||
|
- Con: fragmented client quality; less beginner-friendly than Signal or Matrix
|
||||||
|
|
||||||
### Briar
|
---
|
||||||
|
|
||||||
|
## 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!)
|
- Works over Tor, local WiFi, or Bluetooth (offline!)
|
||||||
- Censorship-resistant by design
|
- Censorship-resistant by design
|
||||||
- Con: Android only (iOS in beta); no desktop client; both parties must be online to first connect
|
- 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?
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Resources
|
## Resources
|
||||||
|
|
||||||
| Resource | Link |
|
| Resource | Link |
|
||||||
| ----------------------------- | ------------------------------------------------------------------------------------------------------ |
|
| --------------------------- | ------------------------------------------------------------------------------------------------------- |
|
||||||
| Signal | [signal.org](https://signal.org) |
|
| Signal | [signal.org](https://signal.org) |
|
||||||
| Matrix spec | [spec.matrix.org](https://spec.matrix.org) |
|
| Element client | [element.io](https://element.io) |
|
||||||
| Element client | [element.io](https://element.io) |
|
| Matrix spec | [spec.matrix.org](https://spec.matrix.org) |
|
||||||
| FluffyChat | [fluffychat.im](https://fluffychat.im) |
|
| Conduit server | [conduit.rs](https://conduit.rs) |
|
||||||
| Conduit server | [conduit.rs](https://conduit.rs) |
|
| Briar | [briarproject.org](https://briarproject.org) |
|
||||||
| Briar | [briarproject.org](https://briarproject.org) |
|
| Privacy Guides | [privacyguides.org/…/real-time-communication](https://www.privacyguides.org/en/real-time-communication) |
|
||||||
| Privacy Guides (comparison) | [privacyguides.org/…/real-time-communication](https://www.privacyguides.org/en/real-time-communication) |
|
| meshtastic-matrix-relay | [github.com/geoffwhittington/meshtastic-matrix-relay](https://github.com/geoffwhittington/meshtastic-matrix-relay) |
|
||||||
| EFF Surveillance Self-Defense | [ssd.eff.org](https://ssd.eff.org) |
|
|
||||||
| meshtastic-matrix-relay | [github.com/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_
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue