Content-Type: multipart/alternative;
 boundary="------------3D72HcmmSYbYicfzIoh4UAAV"
Message-ID: <9eb35cc1-10d2-47b6-9e61-49253b3b9acf@ik.nu>
Date: Thu, 27 Mar 2025 18:47:45 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
From: Ralph Meijer <ralphm@ik.nu>
To: press@meta.com
Jabber-ID: ralphm@ik.nu
Message-ID-Hash: 47GBQJ7NK4EGKCCU5WSEKX372YN76OPB
CC: XMPP Standards Foundation <info@xmpp.org>, XSF Board <board@xmpp.org>
Precedence: list
Reply-To: XSF Board <board@xmpp.org>
Subject: [Board] Open Letter from the XMPP Standards Foundation: Support True
 Messaging Interoperability with XMPP

This is a multi-part message in MIME format.
--------------3D72HcmmSYbYicfzIoh4UAAV
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Dear Meta Team, Tom Alison, Dick Brouwer, Will Cartcart,

The European Digital Markets Act (DMA) is designed to break down walled=20
gardens and enforce messaging interoperability. As a designated=20
gatekeeper, Meta=E2=80=94controlling WhatsApp and Messenger=E2=80=94must =
comply.=20
However, its current proposal falls short, risking further entrenchment=20
of its dominance rather than fostering genuine competition.


    The Problem with Meta=E2=80=99s Interoperability Plan //
    <https://xmpp.org/announcements/open-letter-meta-dma/#the-problem-wit=
h-metas-interoperability-plan>


Meta=E2=80=99s proposed approach relies on restrictive NDAs, proprietary =
APIs,=20
and centralized control. This is *not true interoperability*=E2=80=94it i=
s a=20
closed system that forces third parties to operate within Meta=E2=80=99s =
terms,=20
undermining the spirit of the DMA. Key issues include:

  *

    *Gatekeeper Agreements:* Companies must sign NDAs to access
    interoperability details, creating artificial barriers. Managing
    these legal aspects increases costs for all parties involved.

  *

    *API-Based Control:* APIs limit flexibility, can be modified
    unilaterally, do not scale for true federation, and have to maintaine=
d.

  *

    *User Tracking Risks:* The approach involves compliance issues of
    tracking third-party users at Meta, as well as third-parties
    tracking Meta=E2=80=99s users.

  *

    *Scalability Issues:* Maintaining separate API bridges for each
    provider is inefficient and prevents sustainable competition.


    The Solution: XMPP Federation //
    <https://xmpp.org/announcements/open-letter-meta-dma/#the-solution-xm=
pp-federation>


Meta does not need to reinvent interoperability. The *eXtensible=20
Messaging and Presence Protocol (XMPP)* is a *proven, open standard*=20
that has powered global federated messaging for 25 years. XMPP enables=20
*direct server-to-server communication*, removing the need for=20
restrictive agreements and ensuring:

  *

    *Seamless Federation*: connecting users across providers, just like
    email or phone networks.

  *

    *Decentralized Control*: allowing each service provider to enforce
    its own policies.

  *

    *Enhanced Privacy*: avoiding unnecessary data exposure.

  *

    *Scalability and Flexibility*: ensuring long-term sustainability.


    Meta Has Already Used XMPP=E2=80=94Why Not Now? //
    <https://xmpp.org/announcements/open-letter-meta-dma/#meta-has-alread=
y-used-xmppwhy-not-now>


*WhatsApp was built on an XMPP-based server*, and Meta has previously=20
*supported XMPP in Facebook Messenger*. The protocol is already=20
battle-tested at scale. Furthermore, *Meta is embracing federation for=20
Threads with ActivityPub*, proving that interoperability works when it=20
serves Meta=E2=80=99s strategic interests.

If Threads can federate, so can WhatsApp and Messenger.


    A Call to Action //
    <https://xmpp.org/announcements/open-letter-meta-dma/#a-call-to-actio=
n>

We urge Meta to *adopt XMPP for messaging interoperability*. The *XMPP=20
Standards Foundation (XSF)* is ready to collaborate, continue to evolve=20
the protocol to meet modern needs, and ensure true compliance with the=20
DMA. Let=E2=80=99s build an open, competitive messaging ecosystem=E2=80=94=
one that=20
benefits both users and service providers.

It=E2=80=99s time for real interoperability. Let=E2=80=99s make it happen=
.

Kind regards,

Ralph Meijer
Chair of the Board <https://xmpp.org/about/xsf/people/#chair>
On behalf of the XSF Board and Members

------------------------------------------------------------------------


      Further Reading //
      <https://xmpp.org/announcements/open-letter-meta-dma/#further-readi=
ng>


  * Detailed Technical Briefing
    <https://xmpp.org/announcements/open-letter-meta-dma/technical-briefi=
ng/>
    on the case for XMPP: why Meta must embrace true messaging
    interoperability.


--------------3D72HcmmSYbYicfzIoh4UAAV
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body>
    <div class=3D"page-content">
      <article>
        <p>Dear Meta Team, Tom Alison, Dick Brouwer, Will Cartcart,</p>
        <div class=3D"page-content">
          <article>
            <p>The European Digital Markets Act (DMA) is designed to
              break down walled gardens and enforce messaging
              interoperability. As a designated gatekeeper,
              Meta=E2=80=94controlling WhatsApp and Messenger=E2=80=94mus=
t comply.
              However, its current proposal falls short, risking further
              entrenchment of its dominance rather than fostering
              genuine competition.</p>
            <h2 id=3D"the-problem-with-metas-interoperability-plan"> The
              Problem with Meta=E2=80=99s Interoperability Plan <a
                class=3D"heading-anchor"
href=3D"https://xmpp.org/announcements/open-letter-meta-dma/#the-problem-=
with-metas-interoperability-plan"><i
                  class=3D"fa-solid fa-link fa-xs"></i></a> </h2>
            <p>Meta=E2=80=99s proposed approach relies on restrictive NDA=
s,
              proprietary APIs, and centralized control. This is <strong>=
not
                true interoperability</strong>=E2=80=94it is a closed sys=
tem
              that forces third parties to operate within Meta=E2=80=99s =
terms,
              undermining the spirit of the DMA. Key issues include:</p>
            <ul>
              <li>
                <p><strong>Gatekeeper Agreements:</strong> Companies
                  must sign NDAs to access interoperability details,
                  creating artificial barriers. Managing these legal
                  aspects increases costs for all parties involved.</p>
              </li>
              <li>
                <p><strong>API-Based Control:</strong> APIs limit
                  flexibility, can be modified unilaterally, do not
                  scale for true federation, and have to maintained.</p>
              </li>
              <li>
                <p><strong>User Tracking Risks:</strong> The approach
                  involves compliance issues of tracking third-party
                  users at Meta, as well as third-parties tracking
                  Meta=E2=80=99s users.</p>
              </li>
              <li>
                <p><strong>Scalability Issues:</strong> Maintaining
                  separate API bridges for each provider is inefficient
                  and prevents sustainable competition.</p>
              </li>
            </ul>
            <h2 id=3D"the-solution-xmpp-federation"> The Solution: XMPP
              Federation <a class=3D"heading-anchor"
href=3D"https://xmpp.org/announcements/open-letter-meta-dma/#the-solution=
-xmpp-federation"><i
                  class=3D"fa-solid fa-link fa-xs"></i></a> </h2>
            <p>Meta does not need to reinvent interoperability. The <stro=
ng>eXtensible
                Messaging and Presence Protocol (XMPP)</strong> is a <str=
ong>proven,
                open standard</strong> that has powered global federated
              messaging for 25 years. XMPP enables <strong>direct
                server-to-server communication</strong>, removing the
              need for restrictive agreements and ensuring:</p>
            <ul>
              <li>
                <p><strong>Seamless Federation</strong>: connecting
                  users across providers, just like email or phone
                  networks.</p>
              </li>
              <li>
                <p><strong>Decentralized Control</strong>: allowing each
                  service provider to enforce its own policies.</p>
              </li>
              <li>
                <p><strong>Enhanced Privacy</strong>: avoiding
                  unnecessary data exposure.</p>
              </li>
              <li>
                <p><strong>Scalability and Flexibility</strong>:
                  ensuring long-term sustainability.</p>
              </li>
            </ul>
            <h2 id=3D"meta-has-already-used-xmppwhy-not-now"> Meta Has
              Already Used XMPP=E2=80=94Why Not Now? <a class=3D"heading-=
anchor"
href=3D"https://xmpp.org/announcements/open-letter-meta-dma/#meta-has-alr=
eady-used-xmppwhy-not-now"><i
                  class=3D"fa-solid fa-link fa-xs"></i></a> </h2>
            <p><strong>WhatsApp was built on an XMPP-based server</strong=
>,
              and Meta has previously <strong>supported XMPP in
                Facebook Messenger</strong>. The protocol is already
              battle-tested at scale. Furthermore, <strong>Meta is
                embracing federation for Threads with ActivityPub</strong=
>,
              proving that interoperability works when it serves Meta=E2=80=
=99s
              strategic interests.</p>
            <p>If Threads can federate, so can WhatsApp and Messenger.</p=
>
            <h2 id=3D"a-call-to-action"> A Call to Action <a
                class=3D"heading-anchor"
href=3D"https://xmpp.org/announcements/open-letter-meta-dma/#a-call-to-ac=
tion"><i
                  class=3D"fa-solid fa-link fa-xs"></i></a> </h2>
            <p>We urge Meta to <strong>adopt XMPP for messaging
                interoperability</strong>. The <strong>XMPP Standards
                Foundation (XSF)</strong> is ready to collaborate,
              continue to evolve the protocol to meet modern needs, and
              ensure true compliance with the DMA. Let=E2=80=99s build an=
 open,
              competitive messaging ecosystem=E2=80=94one that benefits b=
oth
              users and service providers.</p>
            <p>It=E2=80=99s time for real interoperability. Let=E2=80=99s=
 make it
              happen.</p>
            <p>Kind regards,<br>
              <br>
              Ralph Meijer<br>
              <a href=3D"https://xmpp.org/about/xsf/people/#chair">Chair
                of the Board</a><br>
              On behalf of the XSF Board and Members</p>
            <hr>
            <h3 id=3D"further-reading"> Further Reading <a
                class=3D"heading-anchor"
href=3D"https://xmpp.org/announcements/open-letter-meta-dma/#further-read=
ing"><i
                  class=3D"fa-solid fa-link fa-xs"></i></a> </h3>
            <ul>
              <li><a
href=3D"https://xmpp.org/announcements/open-letter-meta-dma/technical-bri=
efing/">Detailed
                  Technical Briefing</a> on the case for XMPP: why Meta
                must embrace true messaging interoperability.</li>
            </ul>
          </article>
        </div>
        <p><br>
          <br>
          <br>
        </p>
      </article>
    </div>
    <p><br>
    </p>
  </body>
</html>

--------------3D72HcmmSYbYicfzIoh4UAAV--