WhatsApp Messaging Interoperability

Original Article ↗ Hacker News Discussion ↗

EU rules under the Digital Markets Act are forcing WhatsApp to support interoperability with third‑party messaging apps, but developers note this comes with strict conditions: NDAs, heavy security and legal requirements, and geo‑fencing that limits use to the European Economic Area. Commenters debate whether this tightly controlled model meaningfully opens the platform or mainly protects Meta’s business and data-collection advantages, especially given restrictions on who can build clients and how encryption must be implemented. The thread also contrasts WhatsApp’s approach with alternatives like Signal, Matrix, and XMPP, weighing trade‑offs between strong privacy, open protocols, and practical adoption.

Meta UX and General Annoyances

  • Some complain Meta sites (Facebook/Instagram) “break” the browser back button and view this as user‑hostile design.
  • Others note workarounds (long‑press back button) and that such tangents are technically off‑topic to the interoperability spec.

Hidden Data and iOS Keychain Debate

  • Lengthy side‑thread about “eternal cookies” on iOS: apps (e.g., Facebook/TikTok) persisting data across app deletion, reinstalls, and device restores.
  • Explanation offered: this is iOS Keychain data, which survives app removal and is not user‑visible/editable on iOS.
  • Some see this as a serious tracking/privacy loophole; others note it’s also used for login persistence, trial enforcement, and abuse/fraud prevention.
  • There’s frustration that Apple hasn’t provided user‑level keychain controls or fixed this despite previously signaling intent.

DMA, Geo‑Fencing, and Scope of Interop

  • WhatsApp’s interoperability program is limited to the EU/EEA and requires partner apps to verify users are physically in the EEA at least once every 60 days.
  • Many view this as hostile, minimalist compliance with the DMA and potentially contrary to its spirit.
  • Questions about edge cases (EU citizens traveling, dual residents, VPN use) remain; requirements to pass IPs and user location checks are seen as heavy‑handed.
  • Some argue EU law only applies in the EU so this is legally consistent; others think regulators should push harder, including for iMessage.

Security, Encryption, and Third‑Party Clients

  • WhatsApp demands strict conditions (e.g., NDAs, security teams) for interoperating apps, justified by some as necessary to preserve E2EE guarantees.
  • Others argue this goes beyond “basic security” and effectively excludes small developers and open‑source clients.
  • DMA requires interoperability at the same encryption level as native WhatsApp chats, which some welcome; others distrust any cross‑service E2EE in practice.

Open Protocols and Alternatives

  • Some advocate using open protocols like Matrix or XMPP instead of relying on Meta; others point out they currently leak more metadata than Signal‑style designs.
  • Discussion touches on Signal’s metadata‑minimizing model versus federated systems, and the difficulty of combining strong privacy with federation.
  • Interop between WhatsApp and Matrix/Signal is desired by some but criticized by others who don’t want secure messengers tied to data‑mining ecosystems.

Regulation, Licensing, and Legal Oddities

  • Several commenters praise EU regulation overall (DMA, GDPR, roaming, chargers) while disliking side effects like pervasive cookie banners.
  • The WhatsApp terms banning “viruses” and “copyleft” (GPL/AGPL/LGPL) code are mocked as boilerplate and overbroad; questions arise about GPL’d binaries.
  • Overall sentiment: DMA interoperability is a real step but heavily constrained, lawyered, and far from the “open protocol” many hoped for.