sjat fa7fd32dcd Updated messaging deck

2026-05-10 21:56:22 +02:00

5 KiB

Raw Permalink Blame History

marp	theme	class	paginate
true	gaia	invert	true

Messaging Without Big Tech

Free & Open Alternatives to WhatsApp and Messenger

MakerFLOSS · May 2026

Why Are We Here?

Most people use WhatsApp, Messenger, or iMessage.

WhatsApp — owned by Meta; metadata harvested
Messenger — no E2EE by default in groups; ad tracking
Telegram — not E2EE by default; closed server
iMessage — Apple lock-in; no Android or Linux

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

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

All apps below support end-to-end encryption.

App	Open source	Self-host	No phone#	Federation
Signal	Partial	✗	✗	✗
Matrix / Element	✓	✓	✓	✓
XMPP + OMEMO	✓	✓	✓	✓
Briar	✓	N/A	✓	N/A
Session	✓	Partial	✓	Partial

Signal — The Gold Standard for E2EE

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

Best for: journalists, activists, everyday secure messaging

Signal — Under the Hood

sequenceDiagram
    participant A as Alice's phone
    participant S as Signal Server
    participant B as Bob's phone
    A->>S: encrypted message
    Note over S: sees: who, when, how often<br/>does NOT see: content
    S->>B: encrypted message
    Note over B: decrypts with private key

Metadata still matters — Signal subpoena responses

Matrix — The Federated Open Standard

Matrix is a protocol, not an app — like email for real-time chat.

graph LR
    EC[Element client] --> YH[your homeserver]
    YH <-->|federation| OH[another homeserver]
    FC[FluffyChat] --> OH

Servers: Synapse (Python), Conduit (Rust), Dendrite (Go)
Clients: Element, FluffyChat, Cinny, Fractal, Nheko
Bridges: WhatsApp, Telegram, Signal, IRC, Discord…

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 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
`meshtastic-matrix-relay`	Meshtastic	LoRa mesh ↔ Matrix — off-grid messaging

Catch: Puppeting bridges hold your credentials. WhatsApp's ToS prohibits it — occasional bans occur.

XMPP (Jabber)

The original federated chat standard — 1999. Still alive and kicking.

Extremely mature and lightweight
E2EE via OMEMO
Good clients: Conversations (Android), Monal (iOS/macOS), Gajim (desktop)
Con: fragmented client quality; less beginner-friendly than Signal or Matrix

Briar

Peer-to-peer messaging — no server at all.

Works over Tor, local WiFi, or Bluetooth (offline!)
Censorship-resistant by design
Con: Android-first; no desktop client; both parties must be online to first connect

For: activists, disaster scenarios, high-censorship environments

5 KiB Raw Permalink Blame History