Matrix 2.0 Is Here

Original Article ↗ Hacker News Discussion ↗

Overall sentiment

  • Many are excited that Matrix 2.0 significantly improves speed, VoIP and encryption UX, and narrows the gap with proprietary chat.
  • Others remain skeptical, citing years of rough edges, reliability issues, and stalled ecosystem components (servers, bridges, moderation tools).

Matrix 2.0 features & protocol changes

  • Sliding sync is now native in Synapse and works with both Postgres and SQLite (though SQLite is discouraged for production).
  • MatrixRTC brings native encrypted multiparty VoIP/video; some already rely on Matrix mostly for video calls.
  • “Next Generation Auth” adds native OIDC; some appreciate easier integration with existing IdPs.
  • “Invisible encryption” and standardized terminology aim to hide crypto complexity and reduce confusing UX.
  • New features haven’t yet had full independent security review; audits are planned.

Clients (Element X, web/desktop, alternatives)

  • Element X is praised for performance, better crypto UX, and integration with Element Call, but:
    • Still lacks key features: full audio-call UX, threads, spaces, multi-account support, some notification features.
    • Android users report missing avatars, bad notification stacking, and occasional login/sign‑out bugs.
    • Some treat it as alpha; others say the improvements are transformative.
  • Desktop/web:
    • Current Element Desktop/Web seen as laggy and under-resourced.
    • Plans include reusing the Rust SDK (possibly via WASM or Tauri) and/or evolving the existing web codebase.
    • Other Rust‑SDK clients (e.g. GTK desktop apps) and third‑party clients like FluffyChat and Cinny are mentioned as viable alternatives.

Self‑hosting & server implementations

  • Synapse is the only non‑beta server; Dendrite is effectively on life support due to funding, though still usable.
  • Rust-based Conduit and its forks are active but remain beta.
  • Some lament that a multi‑implementation ecosystem and robust bridge landscape have not fully materialized.
  • matrix-docker-ansible-deploy is praised for breadth (bridges, bots, upgrades) but criticized as overwhelming and finicky.
  • A new “docker compose up” quick‑start for Matrix 2.0/Element stack is being built to ease simple deployments.
  • Managed hosting providers can offload complexity; at least one offers both hosting and the Ansible playbook.

Performance, reliability & notifications

  • Sliding sync is expected to fix many “laggy Element” issues, especially on mobile and small servers.
  • Users still report:
    • Slow sync and message delivery, especially on large or overloaded homeservers.
    • Android battery drain and notification delays or missing notifications.
    • Occasional failures to send or decrypt messages, pushing people back to Signal, Mattermost, or Zulip.
  • Others say notifications on iOS with Element X are already very good, aside from missing quick‑reply.

Security, encryption & privacy

  • Past encryption UX was widely viewed as confusing (recovery keys, device verification). Matrix 2.0 aims to make it “just work,” relying more on QR verification and online backup.
  • There is a standardized key export format; backup/restore via servers is emphasized over manual key juggling.
  • Some want more standardization for cross-client key setup.
  • Pseudo‑IDs to hide global addresses in rooms exist as a proposal and Dendrite implementation but not yet in Synapse/spec.

P2P Matrix & funding

  • True serverless P2P Matrix exists as a prototype “dialect” where the server runs inside the client, but it’s on hiatus due to lack of dedicated funding.
  • Funding today mainly flows via general memberships or buying from supporting orgs; contributors want earmarked funding, crypto wallets, or Kickstarter-style campaigns specifically for P2P.
  • Some criticize claims of “unfunded” status, arguing the project chose not to allocate internal resources.

Moderation, abuse & trust/safety

  • A self‑hoster shut down their homeserver after a CSAM harassment campaign in a public admin room and difficulty cleaning storage; they highlight lack of built‑in preemptive tools (domain blocking, bulk deletion).
  • Others clarify that:
    • Media only lands on a homeserver when a local user fetches it.
    • It is possible to block abusive domains in Synapse config.
  • Still, moderation tooling is described as fragmented and far behind what admins want (IP/CIDR bans, bulk media purge, cross‑room bans).
  • The foundation reportedly prioritizes anti‑abuse work and recently invested in authenticated media to hinder redistribution.

Vision, bridges & adoption

  • Original “bridge everything” vision is seen as partially stalled: many official bridges are outdated or alpha; stable bridges to XMPP, email, SMS are limited.
  • Project insiders say the near‑term priority has shifted to making Matrix itself fast and user‑friendly enough to compete with centralized apps; bridging is secondary for now.
  • Some teams have already migrated away (e.g., to Zulip or Mattermost) citing more reliable mentions, threads, and notifications.
  • Others increasingly see Slack/Discord/Mattermost invites as odd, preferring open protocols, but recognize Matrix still lags on polish and onboarding simplicity.