MakerFLOSS/docs/møder/2026-05-11_messaging-presentation.md

---
marp: true
theme: default
paginate: true
---

# Messaging Without Big Tech

### Free & Open Alternatives to WhatsApp and Messenger

MakerFLOSS · April 2026

---

## Why Are We Here?

Most people use WhatsApp, Messenger, or iMessage.

**What's the problem?**

- **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
- **iMessage** — Apple lock-in; not available on Android or Linux

These apps are _convenient_ — but the cost is your data.

---

## 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       |

---

## 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  | ✗          |

---

## Signal — The Gold Standard for E2EE

**Created by** Moxie Marlinspike (2013), now run by the non-profit Signal Foundation.

**The Signal Protocol** is the encryption layer also used by:
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

---

## Signal — Under the Hood

```
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 does **not** see: message content
- This metadata is still significant — [read the 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 is a **protocol**, not an app — like email, but for real-time chat.

```
[your homeserver]  ←──federation──▶  [another homeserver]
        ▲                                      ▲
   Element client                        FluffyChat client
```

- **Standard**: matrix.org (open spec, anyone can implement)
- **Server software**: Synapse (Python), Conduit (Rust), Dendrite (Go)
- **Clients**: Element, FluffyChat, Cinny, Fractal (GNOME), Nheko
- **Bridges**: WhatsApp, Signal, Slack, Discord, IRC, XMPP — all bridgeable

---

## 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
- Bridges let you consolidate all your chats in one place
- 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
- The UX of Element is still maturing

---

## Matrix — Why It's Interesting for MakerFLOSS

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

---

## Matrix Bridges — Stay Connected During the Transition

A bridge connects Matrix to another network — messages flow both ways.

```
[WhatsApp contact] ←──── WhatsApp servers ────▶ [mautrix-whatsapp bridge] ←──── Matrix ────▶ [You]
```

**You keep your existing accounts. Your contacts don't need to switch.**

| 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                        |

**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)

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_.

- 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

---

## 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                                  |