Repository: xsf/xmpp.org
Pull request #1495: Open Letter to Meta
Author: login: ralphm
Created: 2025-02-28T11:47:19Z | Merged: 2025-03-27T16:49:08Z

This adds an Open Letter to Meta, regarding true messaging interoperability w.r.t. to the EU Digital Markets Act (DMA).



Diff:
diff --git a/config/_default/menus.json b/config/_default/menus.json
index 77e77c491..a084d2d56 100644
--- a/config/_default/menus.json
+++ b/config/_default/menus.json
@@ -173,15 +173,28 @@
             "weight": 6
         },
         {
-            "identifier": "blog",
+            "identifier": "news",
             "name": "News",
-            "url": "/blog/",
             "weight": 7
         },
+        {
+            "identifier": "blog",
+            "name": "Blog",
+            "parent": "news",
+            "url": "/blog/",
+            "weight": 1
+        },
+        {
+            "identifier": "announcements",
+            "name": "Announcements",
+            "parent": "news",
+            "url": "/announcements/",
+            "weight": 2
+        },
         {
             "name": "Jobs",
             "url": "https://xmpp.work",
             "weight": 8
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/content/announcements/_index.md b/content/announcements/_index.md
new file mode 100644
index 000000000..35d1f62a3
--- /dev/null
+++ b/content/announcements/_index.md
@@ -0,0 +1,10 @@
+---
+title: Public Announcments
+layout: single
+aliases:
+    - "/announcements"
+---
+
+We have posted the following public announcements:
+
+2025-03-27: [Open Letter to Meta: Support True Messaging Interoperability with XMPP](open-letter-meta-dma)
diff --git a/content/announcements/open-letter-meta-dma/_index.md b/content/announcements/open-letter-meta-dma/_index.md
new file mode 100644
index 000000000..7b0bced14
--- /dev/null
+++ b/content/announcements/open-letter-meta-dma/_index.md
@@ -0,0 +1,55 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+date: 2025-03-27
+author: Ralph Meijer
+categories: ["Announcement"]
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, 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 maintained.
+
+- **User Tracking Risks:** The approach involves compliance issues of tracking third-party users at Meta, as well as third-parties tracking Meta's users.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for 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—Why Not Now?
+
+**WhatsApp was built on an XMPP-based server**, and Meta has previously **supported XMPP in Facebook Messenger**. The protocol is already battle-tested at scale. Furthermore, **Meta is embracing federation for Threads with ActivityPub**, proving that interoperability works when it serves Meta’s strategic interests.
+
+If Threads can federate, so can WhatsApp and Messenger.
+
+## A Call to Action
+
+We urge Meta to **adopt XMPP for messaging interoperability**. The **XMPP Standards Foundation (XSF)** is ready to collaborate, continue to evolve the protocol to meet modern needs, and ensure true compliance with the DMA. Let’s build an open, competitive messaging ecosystem—one that benefits both users and service providers.
+
+It’s time for real interoperability. Let’s make it happen.
+
+Ralph Meijer  
+[Chair of the Board](/about/xsf/people#chair)  
+On behalf of the XSF Board and Members
+
+***
+
+### Further Reading
+
+- [Detailed Technical Briefing](technical-briefing) on the case for XMPP: why Meta must embrace true messaging interoperability.
diff --git a/content/announcements/open-letter-meta-dma/technical-briefing.md b/content/announcements/open-letter-meta-dma/technical-briefing.md
new file mode 100644
index 000000000..e761f4152
--- /dev/null
+++ b/content/announcements/open-letter-meta-dma/technical-briefing.md
@@ -0,0 +1,272 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+date: 2025-03-27
+author: XMPP Standards Foundation
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, and starting out as an **XMPP service with a locked-in client**, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission included it firmly within the scope of the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
+
+In this spirit—enabling a truly **competitive market** where users can select messaging providers that align with their **budget, business model, and privacy preferences**—we must return to the **core principle of interoperability: the adoption of open communication standards**.
+
+This is the intent behind the DMA’s requirements.
+
+## Why the XSF is Concerned About Meta’s Proposal and Why XMPP is the Solution
+
+Now that Meta has submitted its proposal for messaging interoperability to the European Commission, we have serious concerns that their approach could not only **preserve the status quo** but also **give Meta even more control over user data**.
+
+### Key Concerns with Meta’s Interoperability Proposal
+
+#### 1. Restrictive Access Through NDAs and Agreements
+
+Meta requires companies to **sign a non-disclosure agreement (NDA)** to access their interoperability detailed documents and likely demands an agreement before enabling interoperability between networks. This effectively **keeps companies in a gatekeeper relationship**, just as Meta did when launching *Messenger for Businesses* to control interactions and ensure benefits flowed primarily to them. 
+
+For competitors, **signing an agreement with Meta grants them disproportionate leverage** due to their massive user base. This is **not true interoperability**—it is a **negotiated privilege**, reinforcing Meta’s dominant position.
+
+Requiring an NDA **prevents non-profit organizations like the XSF** from evaluating or contributing to the interoperability mechanism. It **blocks open-source developers from implementing interoperability** in their software, severely limiting innovation.
+
+#### 2. API-Based Approach Instead of Open Protocols
+
+Meta’s proposal appears to be based on **APIs rather than open protocols**. This is a fundamental problem because:
+
+- **Protocols** are designed for **interoperability and cooperation**, ensuring long-term stability.
+- **APIs** are controlled by the provider and offer a **limited set of features**, with associated **usage limits, fees, and restrictions** that can change over time.
+
+The industry has already seen the dangers of relying on APIs—as seen with Twitter, Facebook, and Reddit, where API access was restricted or monetized, disrupting their entire ecosystems. **No sustainable business or long-term project can be built on API access alone.**
+
+#### 3. Client-Side Approach Risks User Tracking
+
+Meta’s approach appears to **force external users to behave as if they are Meta users**, meaning:
+
+- Their **identifiers** would exist within Meta’s system.
+- Through the metadata flowing to their platform, **Meta could track external users**, even if they are not Meta users.
+- If **phone numbers are required as identifiers**, it would enable **cross-platform tracking** and **user matching**, further consolidating Meta’s data collection practices.
+
+This raises serious privacy concerns, particularly for users who explicitly **do not want to be part of Meta’s ecosystem**.
+
+#### 4. The Scalability Problem: API Bridges Do Not Work
+
+Relying on APIs for interoperability is inefficient and **does not scale**. Consider this scenario:
+
+- If a messaging service wants to interoperate with 10 providers, it must **develop and maintain 10 separate API bridges**.
+- This approach is **not sustainable**, as the cost and maintenance overhead would deter smaller players from participating.
+- Worse, **platforms could exploit this loophole to avoid true interoperability**. For example, if Meta and Telegram each offer APIs but neither is willing to implement the other's API, they can both claim they are open to interoperability—while **ensuring that nothing actually happens**. This **completely undermines the intent of the DMA**.
+
+### Understanding federation: A Telephone Analogy: Why Meta’s Approach is Flawed
+
+This is why the **XMPP Standards Foundation (XSF) steps in** and propose to enable interoperability on federation principles which are at the hearth of the Internet majors protocols and allowed it to stay open.
+
+To better understand the shortcomings of Meta’s proposal, we can compare it to another essential communication system: **the global phone network**.
+
+Today, phone networks are **interoperable and federated**. No matter which provider you use, you can call anyone on another network—whether it's a landline or mobile service. **You do not need an account with every provider to communicate.** This seamless federation is possible because:
+
+1. **A standardized common protocol** ensures universal communication.
+2. **A distributed ID attribution system** allows calls to be routed correctly between providers.
+
+The **same model can and should be applied to messaging interoperability**. 
+
+The XMPP Standards Foundation has already done the heavy lifting: by **adopting the XMPP S2S (server-to-server) protocol as the interoperability standard**, we can **achieve the same seamless communication in messaging**.
+
+## Interoperability Through XMPP Federation
+
+The most effective approach to achieving interoperability is **federation**. This is the principle that underpins **email** and **decentralized federated social networks**, such as those using **ActivityPub (e.g., Mastodon)** or custom approaches like **Bluesky**.
+
+Meta argues against **messaging federation**, claiming that they need to **protect their users from spam, abuse, and security threats**. While user protection is important, this **does not mean federation is inherently unsafe**. In fact, **XMPP was designed with these concerns in mind**—its goal is to support a **sustainable, global-scale federated messaging network** with **built-in security, moderation, and control mechanisms**.
+
+### How Federation Works
+
+In a federated system, a user identifier consists of **two components**:
+
+1. **The domain name** – This serves as the **first level of routing** for messages and interactions, much like an email address (e.g., `user@domain123.eu`). It ensures that messages are **delivered to the correct provider**.
+2. **The username, identifier, or key** – This is assigned by the domain’s provider and **routes communication internally** to the specific user. Importantly, **it does not need to expose private information** and can be processed internally to **protect user privacy**.
+
+Federation enables **server-to-server (s2s) communication**, providing a **flexible and privacy-focused** solution for interoperability. With email, knowing a public address (e.g., `user@domain123.eu`) allows communication **without exposing sensitive details** like the user phone number. The same principle applies to federated protocols like **XMPP and ActivityPub**.
+
+### How Federation Enhances Security & Control
+
+A common misconception is that **federation compromises security**. In reality, **federation offers strong safeguards** while still allowing **providers to enforce moderation and control**. 
+
+Federated systems use a **clear separation between internal and external communication**:
+
+1. **Client-to-Server (c2s) Protocol** – Manages communication between **a provider and its internal users**. Users authenticate through this endpoint with their credentials.
+2. **Server-to-Server (s2s) Protocol** – Handles **external communication between providers**, ensuring that **internal user traffic remains isolated** from external threats.
+
+This gives all providers, including Meta, the opportunity to put **multiple layers of protection** in place:
+
+1. **Separation of internal and external traffic**  
+   - Internal user traffic and external communication are processed **on separate endpoints**.
+   - In emergencies, providers can **completely block external traffic** while **keeping internal messaging functional**.
+
+2. **Domain-level moderation and blocking**  
+   - Providers can **ban external domains** that engage in spam, harmful content, or lack proper moderation.  
+
+3. **Improved monitoring and security enforcement**  
+   - Providers can **thoroughly monitor s2s traffic** to **combat spam, DoS attacks, and other security threats**.
+   - Unlike centralized systems, **federation empowers providers to implement their own security policies** without relying on a single entity.
+
+## Meta, Federation, and XMPP
+
+There is no **technical limitation** preventing Meta from supporting **XMPP**—in fact, **Meta has already done so in the past**.
+
+### Meta’s History with XMPP: Proof of Feasibility
+
+Meta (formerly Facebook) has previously supported XMPP in its messaging products:
+
+- **Facebook Messenger** originally supported XMPP but later discontinued compliance. This shift was **not due to technical constraints**, but rather a **strategic decision** to push users into Meta’s proprietary ecosystem, leveraging its massive user base to create a **network effect** in its favor.
+- **WhatsApp** was originally built using an **open-source XMPP server**—which still **forms the core of its infrastructure** today. 
+  - The **protocol used by WhatsApp** is a **direct derivative of XMPP**, where the XML-based tag system was converted into a **binary format** for **compactness**.  
+  - Despite this change, the **fundamental design and semantics remain identical to XMPP**.
+
+### Meta’s Selective Adoption of Federation
+
+Meta has demonstrated a **willingness to adopt federation**—but **only when it suits its strategic interests**.  
+
+For example, **Threads**, Meta’s social media platform, has committed to **supporting ActivityPub and the Fediverse protocol**. The **Fediverse federation and ID system** function in **the same way that XMPP enables messaging federation**.  
+This **raises an important question**:
+If **Meta is willing to embrace federation** for Threads when facing **competition from Twitter/X and Bluesky**, why is it **reluctant to adopt XMPP for messaging interoperability** under the **Digital Markets Act (DMA)?**
+
+The fundamental difference here is not technical. It is strategic:
+
+- In **messaging**, Meta enjoys **market dominance**, with billions of users across **WhatsApp, Messenger, and Instagram**.  
+- In contrast, **Threads is struggling against Twitter/X and Bluesky**—so Meta is embracing federation as a way to level the playing field and gain market share.  
+
+In other words, **Meta embraces open protocols when it benefits from them, but resists them when they threaten its market control**.  
+
+If Meta were genuinely committed to **interoperability**, it would recognize **XMPP as the most viable and proven protocol for federated messaging**—just as it has in the past.
+
+## Building the Future of Messaging
+
+Federation **is not a security risk—it is a scalable, privacy-friendly model** that has already been **proven in global communication networks** like **email and federated social media**. By leveraging the **XMPP server-to-server (s2s) protocol**, messaging services can **achieve true interoperability** while maintaining **security, user privacy, and control**.
+
+### A Call to Meta: Build Your Interoperability Stack on XMPP
+
+We at the XMPP Standards Foundation (XSF) urge Meta to build its interoperability framework on top of XMPP federation.  
+
+If Threads can implement the Fediverse protocol, there is no reason why Meta cannot do the same with XMPP for Facebook Messenger and WhatsApp—especially since WhatsApp itself was originally built on XMPP.
+
+### The XSF Welcomes Collaboration
+
+The XSF is an open and inclusive organization, welcoming contributions from companies, developers, vendors, and network operators. We recognize that, while Messenger and WhatsApp were originally based on XMPP, there may still be technical discussions needed to align the protocol with Meta’s current needs.
+
+If Meta has specific requirements, such as:
+
+- Features unique to Facebook Messenger or WhatsApp
+- Scalability considerations due to the size of Meta’s user base  
+- New extensions to address Meta’s specific use cases  
+
+The XSF is the right place to have these discussions. Our mission is to evolve and improve federated messaging standards.
+
+### Join the Conversation on the Future of Federated Messaging
+
+We understand that Meta may wish to contribute to the development of XMPP, and we would welcome Meta’s most prominent messaging experts to bring their expertise, concerns, and ideas into the work of the XMPP Standards Foundation.
+
+Let’s work together to build a truly interoperable, open, and competitive messaging future.
+
+***
+
+## Contact Information
+
+Press and general inquiries: [info@xmpp.org](mailto:info@xmpp.org)
+
+Ralph Meijer  
+[Chair of the Board](/about/xsf/people#chair)  
+XMPP: [ralphm@ik.nu](xmpp:ralphm@ik.nu)  
+Mail: [ralphm@ik.nu](mailto:ralphm@ik.nu)
+
+Matthew Wild  
+[Executive Director](/about/xsf/people#executive-director)  
+XMPP: [me@matthewwild.co.uk](xmpp:me@matthewwild.co.uk)  
+Mail: [me@matthewwild.co.uk](mailto:me@matthewwild.co.uk)
+
+Mickaël Rémond  
+Member and Rapporteur to the XSF on the DMA  
+XMPP: [mremond@process-one.net](xmpp:mremond@process-one.net)  
+Mail: [mremond@process-one.net](mailto:mremond@process-one.net)
diff --git a/content/blog/open-letter-meta-dma.md b/content/blog/open-letter-meta-dma.md
new file mode 100644
index 000000000..d79be4895
--- /dev/null
+++ b/content/blog/open-letter-meta-dma.md
@@ -0,0 +1,14 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+date: 2025-03-27
+categories: ["XSF", "Open Letter"]
+author: Ralph Meijer
+---
+
+It has been a little over a year since Meta [announced](https://engineering.fb.com/2024/03/06/security/whatsapp-messenger-messaging-interoperability-eu/) their [proposal](https://developers.facebook.com/m/messaging-interoperability/) for third-parties to achieve messaging interoperability with WhatsApp, with Facebook Messenger following half a year later. Not for everyone, and only because these services were designated as Gate Keepers under the recent [Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en) in the EU. So only in the EU, and then with many strings attached. In that time, a lot has been written. Element/Matrix have put in efforts to work with Meta to get some interoperability going. Unfortunately, the reference offers don't provide what we would call true interoperability, and given that virtually nobody has taken up Meta on this offer, their proposal just falls short across the board.
+
+Over at the IETF, the [More Instant Messaging Interoperability (MIMI) working group](https://datatracker.ietf.org/wg/mimi/about/) is working on mechanisms for interoperability. While several of our members are involved with MIMI and working on the implementation of the related [MLS protocol](https://datatracker.ietf.org/wg/mls/about/) for end-to-end encryption, we believe it is time to have true interoperability using a well-tested and widely implemented set of standards: XMPP.
+
+To that end, we today publish an [Open Letter to Meta](/announcements/open-letter-meta-dma/). A call to action, urging Meta to adopt XMPP for messaging interoperability. For a more in-depth reasoning, we also provide a [detailed technical briefing](/announcements/open-letter-meta-dma/technical-briefing).
+
+We are ready. Let's make it happen.
diff --git a/themes/xmpp.org/assets/css/style.css b/themes/xmpp.org/assets/css/style.css
index cb48ad8e4..13011eb66 100644
--- a/themes/xmpp.org/assets/css/style.css
+++ b/themes/xmpp.org/assets/css/style.css
@@ -12,7 +12,10 @@ h5,
 h6,
 .nav-link {
     font-family: "Exo 2", sans-serif;
-    font-weight: 400;
+    font-weight: 700;
+}
+h3 + h4 {
+     margin-top: 1rem;
 }
 .heading-anchor {
     visibility: hidden;
@@ -89,6 +92,10 @@ article h2,
 article h3 {
     color: #002b5c;
 }
+article b,
+article strong {
+    font-weight: 800;
+}
 table {
     background: #fff;
     border: solid 1px #ddd;
@@ -438,7 +445,12 @@ button[name="show-xep-implementations"] {
 	label {
 		color: #acb6bd;
 	}
-	h1, h2, h3, h4, h5, h6 {
+	h1,
+	h2,
+	h3,
+	.sidebar h4,
+	.sidebar h5,
+	.sidebar h6 {
 		color: #95c0d9;
 	}
     .header-internal h1, .header-internal h1 a {
diff --git a/themes/xmpp.org/assets/fonts/font.css b/themes/xmpp.org/assets/fonts/font.css
index 7ab62ff19..3b2b85ae3 100644
--- a/themes/xmpp.org/assets/fonts/font.css
+++ b/themes/xmpp.org/assets/fonts/font.css
@@ -31,13 +31,33 @@
 		url('Exo_2_400.ttf') format('truetype');
 }
 @font-face {
+	font-family: 'Merriweather';
+	font-display: swap;
+	font-style: normal;
+	font-weight: 300;
+	src: url('merriweather-v30-latin-300.woff2') format('woff2');
+}
+
+@font-face {
+	font-display: swap;
 	font-family: 'Merriweather';
 	font-style: normal;
 	font-weight: 400;
-	src:
-		url('merriweather-v22-latin-regular.woff2') format('woff2'),
-		url('merriweather-v22-latin-regular.woff') format('woff'),
-		url('merriweather-v22-latin-regular.eot') format('embedded-opentype'),
-		url('merriweather-v22-latin-regular.svg#Merriweather') format('svg'),
-		url('merriweather-v22-latin-regular.ttf') format('truetype');
+	src: url('merriweather-v30-latin-regular.woff2') format('woff2');
+}
+
+@font-face {
+	font-display: swap;
+	font-family: 'Merriweather';
+	font-style: normal;
+	font-weight: 700;
+	src: url('merriweather-v30-latin-700.woff2') format('woff2');
+}
+
+@font-face {
+	font-display: swap;
+	font-family: 'Merriweather';
+	font-style: normal;
+	font-weight: 900;
+	src: url('merriweather-v30-latin-900.woff2') format('woff2');
 }
diff --git a/themes/xmpp.org/layouts/_default/single_open_letter_meta_dma.html b/themes/xmpp.org/layouts/_default/single_open_letter_meta_dma.html
new file mode 100644
index 000000000..1c0e9f7a5
--- /dev/null
+++ b/themes/xmpp.org/layouts/_default/single_open_letter_meta_dma.html
@@ -0,0 +1,24 @@
+
+{{- define "main" -}}
+<div class="container" role="main">
+  <div class="row justify-content-center">
+    <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
+      <article role="main">
+        <div class="header-internal">
+            <h1><a href="{{- .RelPermalink -}}">{{- .Title -}}</a></h1>
+            {{- partial "post_meta" . -}}
+        </div>
+        <div class="page-content">
+            <article>
+                {{- .Content -}}
+            </article>
+        </div>
+      </article>
+    </div>
+    {{- $currentSection := .Section -}}
+    {{- if $currentSection -}}
+      {{- partial "sidebar_open_letter_meta_dma.html" . -}}
+    {{- end -}}
+  </div>
+</div>
+{{- end -}}
diff --git a/themes/xmpp.org/layouts/partials/footer.html b/themes/xmpp.org/layouts/partials/footer.html
index 07ab7abaa..5a4dbf6c1 100644
--- a/themes/xmpp.org/layouts/partials/footer.html
+++ b/themes/xmpp.org/layouts/partials/footer.html
@@ -51,7 +51,10 @@ <h4>The <a href="/about/xmpp-standards-foundation/">XSF</a> is generously sponso
                         <a href="/community/">Community</a>
                     </li>
                     <li>
-                        <a href="/blog/">News</a>
+                        <a href="/blog/">Blog</a>
+                    </li>
+                    <li>
+                        <a href="/announcements/">Announcements</a>
                     </li>
                     <li>
                         <a href="/about/press-kit/">Press Kit</a>
diff --git a/themes/xmpp.org/layouts/partials/sidebar_open_letter_meta_dma.html b/themes/xmpp.org/layouts/partials/sidebar_open_letter_meta_dma.html
new file mode 100644
index 000000000..caa167551
--- /dev/null
+++ b/themes/xmpp.org/layouts/partials/sidebar_open_letter_meta_dma.html
@@ -0,0 +1,26 @@
+<aside class="col-12 col-lg-2 ml-auto sidebar">
+    <p><a href="/announcements/">« Announcements</a></p>
+    <h4>Open Letter</h4>
+    <ul>
+        <li>
+            <a href="/announcements/open-letter-meta-dma/">The Letter</a>
+        </li>
+        <li>
+            <a href="/announcements/open-letter-meta-dma/technical-briefing">The Technical Briefing</a>
+        </li>
+    </ul>
+
+    <h4>Helpful Links</h4>
+
+    <ul>
+        <li>
+            <a href="/about/xmpp-standards-foundation/">The XSF</a>
+        </li>
+        <li>
+            <a href="/about/press-kit">Press Kit</a>
+        </li>
+        <li>
+            <a href="/contact">Contact</a>
+        </li>
+    </ul>
+</aside>
diff --git a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.eot b/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.eot
deleted file mode 100644
index 7f653336d..000000000
Binary files a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.eot and /dev/null differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.svg b/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.svg
deleted file mode 100644
index 555dea6e5..000000000
--- a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.svg
+++ /dev/null
@@ -1,374 +0,0 @@
-<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
-<svg xmlns="http://www.w3.org/2000/svg">
-<defs >
-<font id="Merriweather" horiz-adv-x="657" ><font-face
-    font-family="Merriweather"
-    units-per-em="1000"
-    panose-1="0 0 5 0 0 0 0 0 0 0"
-    ascent="984"
-    descent="-273"
-    alphabetic="0" />
-<glyph unicode=" " glyph-name="space" horiz-adv-x="237" />
-<glyph unicode="!" glyph-name="exclam" horiz-adv-x="354" d="M205 238H141L111 883H233L205 238ZM107 83T130 104T182 125Q214 125 231 107T248 62Q248 30 226 10T171 -10Q145 -10 126 7T107 53Q107 83 130 104Z" />
-<glyph unicode="&quot;" glyph-name="quotedbl" horiz-adv-x="612" d="M209 456H143L124 827H230L209 456ZM468 456H403L383 827H489L468 456Z" />
-<glyph unicode="#" glyph-name="numbersign" horiz-adv-x="744" d="M81 266H200L219 473H102V532H226L248 743H331L308 532H477L499 743H581L559 532H677V473H552L534 266H655L656 206H526L506 0H424L444 206H275L253 0H170L192 206H81V266ZM301 473L282 266H449L470
-473H301Z" />
-<glyph unicode="$" glyph-name="dollar" horiz-adv-x="659" d="M575 110T519 55T358 -9L357 -126H287L288 -10Q229 -6 175 8T94 34L101 205H164L185 81Q230 43 322 43Q395 43 432 75T470 169Q470 205 449 232T394 281T302 332Q296 336 284 342Q222 374 184 403T124
-472T102 569Q102 642 157 691T301 750V860H372V751Q452 747 534 714L529 554H468L445 670Q430 683 405 691T345 699Q283 699 243 672T203 588Q203 549 225 520T276 473T364 423Q446 377 485 351T549 286T575 192Q575 110 519 55Z" />
-<glyph unicode="%" glyph-name="percent" horiz-adv-x="1037" d="M639 751H715L395 0H319L639 751ZM178 321T137 348T75 422T53 524Q53 590 79 638T151 711T249 736Q340 736 384 679T428 530Q428 465 401 418T330 346T232 321Q178 321 137 348ZM286 373T311 414T336
-526Q336 596 313 639T243 683Q196 683 171 642T146 529Q146 464 170 419T239 373Q286 373 311 414ZM731 20T691 47T629 121T607 224Q607 289 633 337T705 410T803 436Q892 436 936 379T981 230Q981 165 954 118T883 45T785 20Q731 20 691 47ZM838 73T864 114T890
-226Q890 296 867 339T797 383Q750 383 725 342T699 229Q699 163 723 118T791 73Q838 73 864 114Z" />
-<glyph unicode="&amp;" glyph-name="ampersand" horiz-adv-x="756" d="M739 352L658 341Q659 273 638 212T580 112Q614 81 643 66T710 49V5Q701 0 678 -3T638 -6Q603 -6 575 7T509 51Q471 20 422 6T325 -9Q203 -9 132 43T60 187Q60 251 101 297T210 371Q123 481
-123 577Q123 624 149 664T220 728T322 752Q380 752 420 732T481 680T501 614Q501 557 480 517T425 449T329 381Q364 339 420 276T513 176L538 152Q563 184 574 226T585 313Q585 332 584 341L503 352V407H739V352ZM222 539T243 499T299 419Q361 469 386 509T411
-609Q411 646 391 676T321 707Q279 707 251 674T222 590Q222 539 243 499ZM368 47T403 57T465 88Q425 124 378 176T259 312L242 332Q157 266 157 194Q157 130 203 89T333 47Q368 47 403 57Z" />
-<glyph unicode="&apos;" glyph-name="quotesingle" horiz-adv-x="353" d="M209 456H143L124 827H230L209 456Z" />
-<glyph unicode="(" glyph-name="parenleft" horiz-adv-x="430" d="M67 467T114 572T219 742T316 828L358 799Q327 779 283 720T203 560T167 331Q167 199 202 96T283 -69T360 -153L316 -184Q275 -160 219 -101T115 70T67 334Q67 467 114 572Z" />
-<glyph unicode=")" glyph-name="parenright" horiz-adv-x="430" d="M363 178T316 73T211 -97T114 -183L72 -154Q103 -134 147 -75T227 85T263 314Q263 446 228 549T147 714T70 798L114 829Q155 805 211 746T315 575T363 311Q363 178 316 73Z" />
-<glyph unicode="*" glyph-name="asterisk" horiz-adv-x="643" d="M295 567L202 595L76 654L121 733L235 653L308 589L286 683L271 823H366L354 684L334 590L405 655L519 736L565 658L442 598L348 567L442 539L568 482L521 400L409 480L334 545L356 450L371 311L278
-310L289 450L308 545L237 479L124 397L77 476L202 537L295 567Z" />
-<glyph unicode="+" glyph-name="plus" horiz-adv-x="661" d="M295 352L292 437V547H369V437L364 352L440 357H556V281H440L364 284L369 201V84H292V201L295 284L208 281H105V357H208L295 352Z" />
-<glyph unicode="," glyph-name="comma" horiz-adv-x="335" d="M206 150T228 118T250 29Q250 -28 232 -81T187 -171T134 -224H133L99 -200V-189Q119 -173 139 -120T160 -18Q160 -3 155 6T137 29Q123 44 116 57T109 92Q109 118 125 134T167 150H172Q206 150 228 118Z" />
-<glyph unicode="-" glyph-name="hyphen" horiz-adv-x="628" d="M516 284H112V357H516V284Z" />
-<glyph unicode="." glyph-name="period" horiz-adv-x="265" d="M101 -10T82 8T63 54Q63 85 85 106T138 127Q169 127 185 109T202 63Q202 30 180 10T127 -10Q101 -10 82 8Z" />
-<glyph unicode="/" glyph-name="slash" horiz-adv-x="431" d="M122 -177H36L309 781H394L122 -177Z" />
-<glyph unicode="0" glyph-name="zero" horiz-adv-x="643" d="M189 -9T126 79T62 308Q62 406 98 479T196 592T332 631Q462 631 522 548T582 319Q582 222 548 148T453 32T317 -9Q189 -9 126 79ZM470 42T470 309Q470 439 437 509T324 579Q247 579 210 513T173 322Q173
-195 208 119T321 42Q470 42 470 309Z" />
-<glyph unicode="1" glyph-name="one" horiz-adv-x="440" d="M188 516Q167 508 122 497T49 482L39 538Q90 549 143 575T233 632H234L295 622V58L419 49V0H59V49L188 58V516Z" />
-<glyph unicode="2" glyph-name="two" horiz-adv-x="598" d="M139 94T216 161T338 301T384 437Q384 492 351 524T257 557Q200 557 159 535T83 479L51 524Q86 565 151 598T290 632Q360 632 408 607T479 540T502 450Q502 351 407 247T169 59L479 82L514 168L565 158L539
-0H62L47 42Q139 94 216 161Z" />
-<glyph unicode="3" glyph-name="three" horiz-adv-x="560" d="M134 -161T106 -158T59 -149V-92Q92 -102 138 -102Q217 -102 274 -77T362 -9T393 85Q393 153 352 190T224 229L193 221Q160 211 161 212L144 265Q186 273 223 289Q285 315 323 358T361 451Q361 508
-328 534T242 561Q197 561 156 545T84 506L57 551Q85 579 146 605T272 632Q363 632 419 593T475 472Q475 401 419 343T286 258Q296 259 314 259Q373 259 418 237T487 178T512 93Q512 20 468 -38T344 -128T157 -161Q134 -161 106 -158Z" />
-<glyph unicode="4" glyph-name="four" horiz-adv-x="644" d="M395 0H63L37 45Q96 157 182 341T336 680H362L442 637L172 117L132 56L395 70L399 265L484 272V75L625 82V0H484V-161H395V0Z" />
-<glyph unicode="5" glyph-name="five" horiz-adv-x="594" d="M122 -109T154 -109Q225 -109 284 -80T377 0T411 116Q411 277 262 277Q229 277 189 268T118 245L91 264L140 624H425L435 643H497L479 540H214L168 307Q195 321 237 332T321 343Q417 343 472 289T527
-132Q527 53 482 -14T353 -121T164 -161Q121 -161 94 -154V-106Q122 -109 154 -109Z" />
-<glyph unicode="6" glyph-name="six" horiz-adv-x="664" d="M254 -11T196 29T107 139T76 294Q76 420 137 526T293 701T489 786L512 743Q395 706 315 620T206 423Q231 452 275 472T377 493Q481 493 536 432T592 263Q592 190 562 128T473 27T335 -11Q254 -11 196
-29ZM293 431T251 407T193 354Q191 330 191 315Q188 194 223 117T341 40Q387 40 419 68T466 143T482 240Q482 339 446 385T347 431Q293 431 251 407Z" />
-<glyph unicode="7" glyph-name="seven" horiz-adv-x="588" d="M161 -143Q215 -25 264 94T403 433L450 551L154 547L112 414L48 426L69 624H525L546 597Q497 460 409 213T273 -173L161 -143Z" />
-<glyph unicode="8" glyph-name="eight" horiz-adv-x="633" d="M65 242T103 292T219 377Q160 415 128 457T96 564Q96 623 127 665T211 730T323 752Q420 752 479 707T538 587Q538 530 504 482T404 397Q484 352 528 306T572 192Q572 131 537 86T442 15T314 -10Q250
--10 194 10T101 73T65 183Q65 242 103 292ZM188 551T210 523T264 475T356 423Q401 447 427 484T453 564Q453 630 417 667T320 705Q265 705 227 673T188 587Q188 551 210 523ZM466 207T445 234T393 282T306 330Q278 344 264 352Q217 328 188 288T159 202Q159 128
-202 85T321 41Q357 41 390 57T445 103T466 171Q466 207 445 234Z" />
-<glyph unicode="9" glyph-name="nine" horiz-adv-x="660" d="M415 632T473 594T559 488T588 337Q588 205 532 96T386 -81T194 -167L171 -123Q287 -85 360 0T459 198Q434 169 391 149T298 128Q229 128 178 157T98 241T70 368Q70 439 101 499T192 595T331 632Q415
-632 473 594ZM373 189T415 214T471 269L474 315Q474 437 442 509T324 581Q278 581 246 554T197 482T181 389Q181 286 218 238T319 189Q373 189 415 214Z" />
-<glyph unicode=":" glyph-name="colon" horiz-adv-x="344" d="M139 403T121 420T102 466Q102 498 124 518T177 539Q208 539 224 521T240 476Q240 443 219 423T165 403Q139 403 121 420ZM139 -10T121 8T102 54Q102 85 124 106T177 127Q207 127 223 109T240 63Q240
-30 219 10T165 -10Q139 -10 121 8Z" />
-<glyph unicode=";" glyph-name="semicolon" horiz-adv-x="344" d="M141 403T122 420T103 466Q103 497 125 518T178 539Q209 539 225 521T242 476Q242 443 220 423T167 403Q141 403 122 420ZM206 150T228 118T250 29Q250 -28 232 -81T187 -171T134 -224H133L99
--200V-189Q119 -173 139 -120T160 -18Q160 -3 155 6T137 29Q123 44 116 57T109 92Q109 118 125 134T167 150H172Q206 150 228 118Z" />
-<glyph unicode="&lt;" glyph-name="less" horiz-adv-x="669" d="M555 488L176 301L555 114V27L82 273V328L555 575V488Z" />
-<glyph unicode="=" glyph-name="equal" horiz-adv-x="653" d="M552 402H102V474H552V402ZM552 127H102V199H552V127Z" />
-<glyph unicode="&gt;" glyph-name="greater" horiz-adv-x="669" d="M114 27V114L493 301L114 488V575L587 328V273L114 27Z" />
-<glyph unicode="?" glyph-name="question" horiz-adv-x="487" d="M158 276T150 312T139 379Q139 418 168 447T255 514Q295 541 316 557T353 594Q353 600 355 624T358 658Q358 703 332 744T254 810T133 835Q90 835 57 820L42 882Q59 892 93 899T164 906Q310 906
-381 838T452 662Q452 615 433 579T386 519T316 464Q284 441 267 426T240 394Q239 386 239 367Q239 288 244 242H173Q158 276 150 312ZM158 -10T139 7T120 53Q120 83 143 104T196 125Q227 125 244 107T262 62Q262 30 240 10T184 -10Q158 -10 139 7Z" />
-<glyph unicode="@" glyph-name="at" horiz-adv-x="1078" d="M93 344T163 477T355 685T621 760Q725 760 805 718T931 592T977 390Q977 267 929 176T813 37T696 -11Q669 -11 647 12T624 76Q621 127 637 218Q602 122 550 55T443 -13Q409 -13 377 11T326 80T306 186Q306
-259 337 335T427 462T561 513Q588 513 620 506T678 484Q687 511 701 508Q719 503 737 496L758 489Q711 269 705 165Q704 153 704 133Q704 97 710 79T727 61Q767 61 810 99T882 207T912 366Q912 482 868 555T750 662T588 696Q473 696 377 633T224 455T167 192Q167
-69 208 -17T321 -147T484 -191Q540 -191 600 -177T689 -144L706 -181Q667 -213 603 -233T467 -253Q353 -253 269 -201T139 -52T93 175Q93 344 163 477ZM395 157T412 115T464 72Q487 72 516 103T574 187T623 299Q646 365 653 411Q640 425 603 436T540 448Q495 448
-462 414T412 325T395 210Q395 157 412 115Z" />
-<glyph unicode="A" glyph-name="A" horiz-adv-x="692" d="M290 749H400L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49L49 59L290 749ZM353 589L328 677L304 587L203 266H458L353 589Z" />
-<glyph unicode="B" glyph-name="B" horiz-adv-x="685" d="M129 681L47 693V743H182Q216 743 268 747Q316 751 339 751Q477 751 536 708T596 582Q596 511 555 460T443 396Q539 398 594 351T649 223Q649 122 578 58T341 -6Q305 -6 272 -3Q194 0 179 0H46V49L129
-59V681ZM249 414T292 414H347Q417 414 453 453T489 564Q489 634 453 666T330 699Q294 699 256 695L235 693V415Q249 414 292 414ZM258 48T339 48Q440 48 485 89T531 209Q531 286 492 321T364 356Q262 356 235 354V56Q258 48 339 48Z" />
-<glyph unicode="C" glyph-name="C" horiz-adv-x="653" d="M268 -11T191 36T73 170T33 372Q33 484 80 570T209 703T393 751Q470 751 578 727L611 721L601 541H534L509 668Q495 680 461 688T376 697Q312 697 262 661T184 553T155 383Q155 289 180 212T256 90T382
-44Q435 44 463 53T512 79L554 177L617 169L593 27Q572 26 531 13Q495 2 462 -4T378 -11Q268 -11 191 36Z" />
-<glyph unicode="D" glyph-name="D" horiz-adv-x="758" d="M129 681L51 693V743H182Q213 743 271 747Q329 751 358 751Q544 751 634 658T725 395Q725 277 679 186T548 43T355 -8Q331 -8 273 -4Q213 0 183 0H46V49L129 59V681ZM270 48T325 48H355Q430 49 487 86T577
-196T609 375Q609 533 541 615T334 697Q305 697 265 693Q248 690 235 690V56Q270 48 325 48Z" />
-<glyph unicode="E" glyph-name="E" horiz-adv-x="651" d="M129 681L47 693V743H556L570 588H513L484 685L236 691V409L403 412L417 495H472V265H417L403 351L236 354V56L518 66L571 192L630 174L601 0H46V49L129 59V681Z" />
-<glyph unicode="F" glyph-name="F" horiz-adv-x="619" d="M129 681L43 693V743H578L588 573H523L493 684L236 691V401L417 404L434 487H487V253H435L417 340L236 344V59L392 49V0H49V49L129 59V681Z" />
-<glyph unicode="G" glyph-name="G" horiz-adv-x="740" d="M282 -11T204 37T84 169T43 361Q43 484 91 572T226 705T422 751Q523 751 655 720L646 547H575L551 667Q537 678 504 688T414 698Q341 698 285 662T198 555T166 383Q166 290 191 213T269 90T398 43Q446
-43 489 54T555 85V308L429 318V377H721V318L663 309V40Q641 39 590 23Q538 7 492 -2T390 -11Q282 -11 204 37Z" />
-<glyph unicode="H" glyph-name="H" horiz-adv-x="828" d="M131 681L52 693V743H324V693L238 681V412H590V681L509 693V743H777V693L698 681V59L777 49V0H508V49L590 59V350H238V59L325 49V0H50V49L131 59V681Z" />
-<glyph unicode="I" glyph-name="I" horiz-adv-x="403" d="M147 681L54 693V743H348V693L255 681V59L348 48V0H55V49L147 59V681Z" />
-<glyph unicode="J" glyph-name="J" horiz-adv-x="381" d="M38 -124T73 -91T124 -8Q137 30 141 80T145 236V680L49 693V743H343V693L252 680V275V228Q252 149 250 101T241 19Q223 -61 162 -113T21 -179L-6 -137Q38 -124 73 -91Z" />
-<glyph unicode="K" glyph-name="K" horiz-adv-x="726" d="M567 0T541 40T465 168Q459 179 432 227T381 311T339 366L238 252V59L329 49V0H48V49L131 59V681L49 693V743H321V693L238 681V331L532 681L448 693V743H695V693L618 681L402 439Q437 409 476 352T573
-205Q622 128 644 96T680 60L727 49V0H584Q567 0 541 40Z" />
-<glyph unicode="L" glyph-name="L" horiz-adv-x="634" d="M131 681L50 693V743H337V693L238 681V59L496 68L555 236L616 227L581 0H48V49L131 59V681Z" />
-<glyph unicode="M" glyph-name="M" horiz-adv-x="990" d="M164 681L55 693V743H320L461 293L494 166L524 293L664 743H927V693L817 681L897 60L984 49V0H696V49L787 59L742 508L721 701L679 557L512 34H447L285 513L226 702L208 508L168 59L267 49V0H6V49L91 59L164 681Z" />
-<glyph unicode="N" glyph-name="N" horiz-adv-x="799" d="M130 681L50 693V743H236L569 255L625 149V681L538 693V743H774V693L694 681V0H615L275 499L198 631V59L293 49V0H50V49L130 60V681Z" />
-<glyph unicode="O" glyph-name="O" horiz-adv-x="722" d="M247 -11T177 36T70 168T34 367Q34 482 77 569T197 703T368 751Q524 751 606 653T689 380Q689 263 645 175T523 38T349 -11Q247 -11 177 36ZM265 699T209 615T153 367Q153 217 207 130T360 42Q456 42 512
-129T569 379Q569 530 515 614T362 699Q265 699 209 615Z" />
-<glyph unicode="P" glyph-name="P" horiz-adv-x="649" d="M131 681L53 693V743H186Q222 743 257 746Q311 750 359 750Q504 749 564 696T624 536Q624 456 587 397T485 307T334 276Q305 276 275 277T238 280V60L375 49V0H48V49L131 59V681ZM266 330T334 330Q413
-330 462 378T512 535Q512 621 469 658T335 696Q303 696 267 692Q245 690 238 690V335Q266 330 334 330Z" />
-<glyph unicode="Q" glyph-name="Q" horiz-adv-x="727" d="M764 -198T724 -183T652 -147T574 -90Q525 -52 492 -31T423 -3Q386 -11 351 -11Q250 -11 179 36T72 168T36 367Q36 482 79 569T199 703T371 751Q527 751 609 653T691 380Q691 251 638 157T493 20Q538 16
-580 -2T679 -53Q742 -87 781 -103T861 -119Q878 -119 892 -117L904 -160Q886 -179 861 -188T809 -198Q764 -198 724 -183ZM459 42T515 128T571 379Q571 530 517 614T365 699Q268 699 212 615T155 367Q155 217 209 130T362 42Q459 42 515 128Z" />
-<glyph unicode="R" glyph-name="R" horiz-adv-x="704" d="M46 49L129 59V681L51 694V743H182Q210 743 258 747Q308 751 336 751Q483 751 545 704T608 554Q608 483 569 424T460 344Q492 327 519 286T587 170Q618 114 634 88T666 59L705 49V0H567Q551 0 531 34T478
-141Q442 220 416 266T363 326Q256 326 236 327V59L335 49V0H46V49ZM419 380T456 422T493 547Q493 620 456 658T326 697Q294 697 262 693Q242 691 236 691V381Q251 380 298 380H355Q419 380 456 422Z" />
-<glyph unicode="S" glyph-name="S" horiz-adv-x="594" d="M238 -11T197 -2T107 22Q77 33 62 34L70 215H134L151 85Q168 69 206 57T291 44Q367 44 406 78T446 172Q446 211 425 239T368 287T270 334Q214 359 173 385T101 454T70 559Q70 614 99 657T184 726T314 751Q360
-751 395 744T476 725Q496 718 510 716L504 548H443L423 671Q413 681 382 690T313 699Q244 699 209 670T173 586Q173 546 194 519T248 473T350 421Q415 390 456 365T526 300T556 203Q556 150 527 101T437 21T290 -11Q238 -11 197 -2Z" />
-<glyph unicode="T" glyph-name="T" horiz-adv-x="692" d="M290 690L118 684L83 475H17L34 743H657L669 475H606L573 684L400 690V59L542 49V0H160V49L290 59V690Z" />
-<glyph unicode="U" glyph-name="U" horiz-adv-x="740" d="M234 -8T165 70T95 314V681L24 693V743H291V693L206 680V303Q206 167 254 107T394 47Q485 47 530 111T576 297V680L492 693V743H725V693L652 681V302Q652 146 578 69T381 -8Q234 -8 165 70Z" />
-<glyph unicode="V" glyph-name="V" horiz-adv-x="670" d="M-16 743H250V693L161 681L326 212L363 90L396 214L545 681L466 693V743H689V693L625 681L388 -8H301L45 681L-16 693V743Z" />
-<glyph unicode="W" glyph-name="W" horiz-adv-x="1000" d="M-19 743H252V693L158 681L295 215L324 76L357 215L472 596L445 681L374 693V743H655V693L557 681L692 215L726 65L754 215L880 681L781 693V743H1019V693L953 681L754 -5H656L503 496L355 -5H260L47
-680L-19 693V743Z" />
-<glyph unicode="X" glyph-name="X" horiz-adv-x="712" d="M303 371L95 680L21 693V743H319V693L224 680L380 427L536 681L448 693V743H694V693L614 680L411 390L634 59L710 49V0H413V49L506 59L336 332L173 59L273 49V0H7V49L92 59L303 371Z" />
-<glyph unicode="Y" glyph-name="Y" horiz-adv-x="644" d="M273 289L48 680L-12 693V743H249V693L170 681L311 413L343 337L379 413L512 681L430 693V743H658V693L593 681L384 290V60L496 49V0H164V49L273 59V289Z" />
-<glyph unicode="Z" glyph-name="Z" horiz-adv-x="654" d="M480 695L184 684L133 551L76 559L98 746H583L606 703L226 127L159 53L505 71L557 228L616 215L593 0H61L34 44L422 624L480 695Z" />
-<glyph unicode="[" glyph-name="bracketleft" horiz-adv-x="428" d="M96 748T105 768T134 796T190 804Q260 804 338 786V744H187V-76H338V-118Q265 -137 190 -137Q154 -137 135 -130T106 -102T96 -40V707Q96 748 105 768Z" />
-<glyph unicode="\" glyph-name="backslash" horiz-adv-x="431" d="M302 -177L30 781H115L388 -177H302Z" />
-<glyph unicode="]" glyph-name="bracketright" horiz-adv-x="428" d="M332 -81T323 -101T294 -129T238 -137Q161 -137 90 -118V-76H240V744H90V786Q168 804 238 804Q274 804 293 797T322 769T332 707V-40Q332 -81 323 -101Z" />
-<glyph unicode="^" glyph-name="asciicircum" horiz-adv-x="666" d="M579 133H496L332 641L169 133H86L287 748H377L579 133Z" />
-<glyph unicode="_" glyph-name="underscore" horiz-adv-x="835" d="M-10 -183V-122H845V-183H-10Z" />
-<glyph unicode="`" glyph-name="grave" horiz-adv-x="333" d="M156 665T85 726T-7 821L65 884L227 686L189 653H188Q156 665 85 726Z" />
-<glyph unicode="a" glyph-name="a" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486 -5T432 -10Q404
--10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73Z" />
-<glyph unicode="b" glyph-name="b" horiz-adv-x="607" d="M-2 800L158 819H160L183 804V503Q213 532 254 551T347 570Q407 570 456 541T535 451T565 297Q565 211 530 141T428 30T275 -11Q206 -11 149 2T80 27V747L-2 758V800ZM268 499T236 482T183 442V74Q189
-60 217 52T282 43Q359 43 406 105T453 286Q453 393 412 446T306 499Q268 499 236 482Z" />
-<glyph unicode="c" glyph-name="c" horiz-adv-x="513" d="M33 357T65 424T161 530T314 570Q357 570 388 562T462 540L458 386H393L371 488Q365 516 295 516Q225 516 185 460T144 299Q144 181 189 120T308 58Q350 58 387 71T452 102L471 62Q444 34 392 12T285 -11Q203
--11 147 26T62 127T33 274Q33 357 65 424Z" />
-<glyph unicode="d" glyph-name="d" horiz-adv-x="621" d="M201 -11T151 19T72 111T42 264Q42 349 77 419T177 529T332 570Q383 570 425 559V746L323 758V801L503 819H506L528 803V51H586V5Q554 -2 531 -6T481 -10Q455 -10 444 -1T433 37V69Q405 35 360 12T261
--11Q201 -11 151 19ZM340 60T374 77T425 118V484Q417 496 388 505T325 515Q247 515 201 456T154 272Q154 164 195 112T301 60Q340 60 374 77Z" />
-<glyph unicode="e" glyph-name="e" horiz-adv-x="544" d="M170 -11T107 68T43 279Q43 366 76 432T168 534T304 570Q397 570 448 519T503 371Q503 310 496 278H152Q154 179 198 119T323 58Q363 58 406 72T474 107L493 63Q464 33 407 11T291 -11Q170 -11 107 68ZM393
-331Q396 352 396 374Q395 439 369 476T285 514Q227 514 193 472T153 331H393Z" />
-<glyph unicode="f" glyph-name="f" horiz-adv-x="400" d="M125 489H31V535L125 554V601Q125 663 157 715T242 797T354 828Q388 828 413 819V719Q404 727 378 734T319 742Q272 742 251 718T229 633V554H367V489H229V57L340 49V0H40V49L125 58V489Z" />
-<glyph unicode="g" glyph-name="g" horiz-adv-x="607" d="M156 -270T99 -230T41 -118Q41 -74 68 -37T134 19Q88 45 88 103Q88 139 109 171T164 220Q114 242 88 283T61 380Q61 438 93 481T179 547T293 570Q394 570 451 528Q466 543 497 557T563 571H597V483H487Q511
-446 511 397Q511 338 482 293T400 222T281 197Q238 197 204 206Q190 192 181 175T172 142Q172 106 196 93T282 79H395Q492 79 539 42T586 -63Q586 -120 545 -167T435 -242T284 -270Q156 -270 99 -230ZM405 252T405 387Q405 454 376 485T287 517Q232 517 200 487T168
-389Q168 326 198 289T291 252Q405 252 405 387ZM342 -212T385 -198T456 -155T483 -88Q483 -43 459 -23T366 -2H248Q208 -2 185 3Q144 -42 144 -98Q144 -154 178 -183T293 -212Q342 -212 385 -198Z" />
-<glyph unicode="h" glyph-name="h" horiz-adv-x="659" d="M99 746L15 757V800L178 819H180L202 804V572L198 487Q230 516 286 542T399 568Q462 568 497 544T546 471T560 337V58L630 49V0H391V49L456 58V338Q456 397 448 430T418 480T352 497Q316 497 275 479T203
-437V58L272 49V0H39V49L99 57V746Z" />
-<glyph unicode="i" glyph-name="i" horiz-adv-x="333" d="M131 655T115 673T99 719Q99 751 118 772T172 793Q206 793 222 775T238 729Q238 695 219 675T164 655H163Q131 655 115 673ZM123 478L47 496V549L202 568H204L227 550V57L307 49V0H42V49L123 58V478Z" />
-<glyph unicode="j" glyph-name="j" horiz-adv-x="317" d="M131 655T115 673T99 719Q99 751 118 772T172 793Q206 793 222 775T238 729Q238 695 219 675T163 655H162Q131 655 115 673ZM42 549L197 568H199L221 550V7Q221 -76 197 -132T132 -216T40 -243Q1 -243
--6 -239L-11 -192Q-3 -193 12 -190T44 -181Q85 -167 101 -114T118 30V475L42 493V549Z" />
-<glyph unicode="k" glyph-name="k" horiz-adv-x="600" d="M98 746L20 757V800L179 819H180L202 804V315L200 256L431 495L356 509V555H598V509L519 495L372 352L562 57L624 49V0H381V49L444 58L303 290L200 188L202 137V58L273 49V0H35V49L98 58V746Z" />
-<glyph unicode="l" glyph-name="l" horiz-adv-x="333" d="M118 746L37 757V800L198 819H200L222 804V57L307 49V0H37V49L118 58V746Z" />
-<glyph unicode="m" glyph-name="m" horiz-adv-x="995" d="M44 49L105 58V478L33 496V550L176 568L194 555L200 515L199 483Q234 515 294 541T403 568Q457 568 490 550T540 494Q572 521 629 544T737 568Q799 568 834 545T883 472T898 339V58L970 49V0H732V49L794
-58V336Q794 394 786 428T754 480T686 497Q653 497 616 483T553 448Q562 409 562 337V58L633 49V0H391V49L457 58V338Q457 398 450 431T421 480T357 497Q321 497 281 479T210 437V58L277 49V0H44V49Z" />
-<glyph unicode="n" glyph-name="n" horiz-adv-x="664" d="M105 478L33 496V550L176 568H179L200 550V508L199 484Q235 516 294 542T407 568Q470 568 504 544T553 471T567 337V57L637 50V0H400V49L462 57V338Q462 397 454 430T424 480T360 497Q324 497 283 479T210
-437V58L278 49V0H42V49L105 58V478Z" />
-<glyph unicode="o" glyph-name="o" horiz-adv-x="608" d="M45 369T82 435T179 535T309 570Q435 570 498 490T562 280Q562 189 525 123T428 23T298 -11Q172 -11 109 69T45 279Q45 369 82 435ZM373 46T410 103T447 272Q447 383 413 448T304 513Q235 513 198 456T160
-287Q160 176 195 111T304 46Q373 46 410 103Z" />
-<glyph unicode="p" glyph-name="p" horiz-adv-x="628" d="M586 212T551 142T451 30T299 -11Q275 -11 247 -7T202 3L205 -81V-182L309 -193V-242H30V-193L102 -182V478L29 496V550L171 568H173L194 550V491Q224 524 268 547T368 570Q427 570 476 541T556 451T586
-297Q586 212 551 142ZM289 500T256 484T205 449V72Q212 60 240 51T303 41Q380 41 427 102T475 286Q475 394 434 447T327 500Q289 500 256 484Z" />
-<glyph unicode="q" glyph-name="q" horiz-adv-x="609" d="M313 -195L424 -184V-23L427 59Q397 29 355 9T261 -11Q202 -11 152 19T72 112T42 267Q42 352 77 421T177 530T332 570Q390 570 454 552L509 567L528 550V-185L597 -195V-242H313V-195ZM341 56T373 72T424
-109V488Q418 500 388 509T324 519Q248 519 202 459T155 274Q155 167 196 112T303 56Q341 56 373 72Z" />
-<glyph unicode="r" glyph-name="r" horiz-adv-x="458" d="M47 49L122 55V478L50 496V550L188 568H190L212 550V532L209 454H212Q222 471 248 498T315 547T404 570Q424 570 437 565V453Q430 458 415 462T380 467Q297 467 226 416V56L353 48V0H47V49Z" />
-<glyph unicode="s" glyph-name="s" horiz-adv-x="505" d="M138 80Q148 65 180 53T249 41Q306 41 333 63T360 124Q360 151 343 171T296 206T208 244Q131 273 96 313T60 420Q60 464 86 497T159 548T263 567Q309 567 343 560T399 546T427 537V413H366L346 487Q340
-499 314 507T256 516Q211 516 184 496T156 442Q156 412 170 393T207 361T267 333L287 325Q343 303 378 283T436 231T460 151Q460 77 403 33T245 -11Q196 -11 143 2T55 30V158H120L138 80Z" />
-<glyph unicode="t" glyph-name="t" horiz-adv-x="407" d="M159 -10T131 16T103 105V489H31V534Q36 535 59 541T90 552Q106 561 115 588Q123 607 134 649T147 699H206L208 555H375V489H208V182Q208 125 211 102T226 72T266 65Q293 65 325 72T376 87L391 42Q367
-24 314 7T216 -10Q159 -10 131 16Z" />
-<glyph unicode="u" glyph-name="u" horiz-adv-x="632" d="M472 -9T459 2T445 38V72Q412 39 363 14T263 -11Q170 -11 131 39T92 204V494L36 510V554L176 567H177L196 555V212Q196 154 204 122T234 74T297 58Q337 58 372 75T433 115V494L361 510V554L513 567H514L537
-555V51H597L596 6Q568 -1 548 -5T500 -9Q472 -9 459 2Z" />
-<glyph unicode="v" glyph-name="v" horiz-adv-x="568" d="M-1 555H231V508L160 495L261 207L303 80L339 203L440 495L372 508V555H575V508L523 495L330 -8H245L44 495L-1 508V555Z" />
-<glyph unicode="w" glyph-name="w" horiz-adv-x="839" d="M-7 555H226V508L150 496L233 202L262 75L291 203L387 555H485L584 203L613 74L645 202L726 495L650 508V555H853V508L800 495L645 -8H551L445 345L419 469L398 345L297 -8H204L44 496L-7 508V555Z" />
-<glyph unicode="x" glyph-name="x" horiz-adv-x="595" d="M244 277L75 496L19 508V555H273V508L203 496L294 367L322 324L349 367L444 496L371 508V555H582V508L522 496L356 289L533 57L591 48V0H334V48L400 58L309 193L279 238L252 194L156 58L239 48V0H6V48L73
-58L244 277Z" />
-<glyph unicode="y" glyph-name="y" horiz-adv-x="572" d="M109 -249T93 -247T69 -241V-154Q75 -158 92 -160T126 -162Q174 -162 210 -129T281 0H233L43 495L-3 508V555H238V508L161 496L259 201L305 55L348 202L437 496L370 508V555H571V508L521 496Q374 46 348
--15Q314 -101 286 -149T220 -223T126 -249Q109 -249 93 -247Z" />
-<glyph unicode="z" glyph-name="z" horiz-adv-x="554" d="M146 491L128 396H67V555H492L512 512L218 118L149 56L418 65L460 177L518 170L500 0H51L30 44L329 434L395 498L146 491Z" />
-<glyph unicode="{" glyph-name="braceleft" horiz-adv-x="508" d="M229 -137T188 -105T146 -11Q146 22 152 51T172 118Q183 151 189 175T195 224Q195 250 185 267T144 293T57 302V376Q115 376 144 383T184 404T195 444Q195 469 190 492T172 551Q159 589 153 617T146
-679Q146 742 187 774T318 806Q345 806 370 802T431 788V742Q424 743 400 744T361 745Q247 745 247 662Q247 629 264 559Q282 481 282 442Q282 396 243 371T144 336Q203 328 242 300T282 226Q282 202 278 176T264 111Q247 41 247 7Q247 -76 361 -76Q376 -76 396
--75T431 -73V-119Q396 -128 371 -132T318 -137Q229 -137 188 -105Z" />
-<glyph unicode="|" glyph-name="bar" horiz-adv-x="422" d="M252 -91H170V869H252V-91Z" />
-<glyph unicode="}" glyph-name="braceright" horiz-adv-x="508" d="M163 -137T138 -133T77 -119V-73Q91 -74 111 -75T147 -76Q261 -76 261 7Q261 41 244 111Q235 149 231 175T226 226Q226 272 265 300T364 336Q304 345 265 370T226 442Q226 481 244 559Q261 629
-261 662Q261 745 147 745Q133 745 109 744T77 742V788Q112 797 137 801T190 806Q278 806 320 774T362 679Q362 646 356 618T336 551Q325 518 319 494T313 445Q313 419 323 405T362 383T450 376V302Q394 302 364 293T324 267T313 224Q313 198 319 174T336 117Q349
-79 355 51T362 -11Q362 -137 190 -137Q163 -137 138 -133Z" />
-<glyph unicode="~" glyph-name="asciitilde" horiz-adv-x="692" d="M125 323T167 351T259 379Q291 379 315 367T369 332Q392 314 408 305T443 296Q502 296 545 353L584 311Q563 273 522 246T432 218Q401 218 378 230T327 264Q304 283 287 292T249 302Q191 302
-145 245L107 288Q125 323 167 351Z" />
-<glyph unicode="&#xa0;" glyph-name="uni00A0" horiz-adv-x="237" />
-<glyph unicode="&#xa1;" glyph-name="exclamdown" horiz-adv-x="354" d="M247 608T224 587T172 566Q140 566 123 584T106 629Q106 661 128 681T183 701Q209 701 228 684T247 638Q247 608 224 587ZM148 453H214L243 -181H121L148 453Z" />
-<glyph unicode="&#xa2;" glyph-name="cent" horiz-adv-x="582" d="M70 352T98 416T183 520T318 568L326 683H391L382 569Q425 565 459 554T500 540L494 386H430L408 488Q402 516 332 516Q263 516 223 460T182 299Q182 181 227 120T345 58Q387 58 425 71T489 102L508
-62Q484 36 437 15T339 -11L333 -119H269L275 -7Q176 8 123 85T70 275Q70 352 98 416Z" />
-<glyph unicode="&#xa3;" glyph-name="sterling" horiz-adv-x="743" d="M193 499Q193 573 226 630T315 719T440 751Q497 751 544 735T620 693L568 617Q562 628 540 645T485 676T415 690Q302 690 302 523V430H455V375H302V268Q302 210 286 170T242 100Q278 97 343
-83Q384 74 414 69T475 64Q536 64 559 87T583 162Q583 190 576 216T558 253H668Q676 243 682 222T688 173Q688 126 662 85T590 18T486 -7Q442 -7 406 2T319 28Q278 42 251 48T196 56Q147 0 100 0Q80 0 65 10T49 41Q49 60 65 77T109 103T166 112Q177 129 185 171T193
-254V375H94V430H193V499Z" />
-<glyph unicode="&#xa4;" glyph-name="currency" horiz-adv-x="755" d="M164 300T164 373Q164 448 205 506L99 612L153 667L259 560Q313 596 376 596Q439 596 496 562L602 667L656 613L552 510Q593 455 593 382Q593 306 549 248L654 144L600 89L495 195Q438 159
-376 159Q314 159 258 192L153 87L99 142L203 245Q164 300 164 373ZM441 235T475 275T510 376Q510 415 492 448T442 500T374 520Q312 520 278 478T243 374Q243 336 261 304T309 254T376 235Q441 235 475 275Z" />
-<glyph unicode="&#xa5;" glyph-name="yen" horiz-adv-x="769" d="M121 685L57 698V743H322V698L249 687L377 473L407 411L442 474L558 687L482 698V743H712V698L641 685L467 410H665V357H440V229H665V175H440V56L554 45V0H230V45L341 56V175H117V229H341V357H117V410H306L121
-685Z" />
-<glyph unicode="&#xa6;" glyph-name="brokenbar" horiz-adv-x="422" d="M252 464H170V869H252V464ZM252 -91H170V313H252V-91Z" />
-<glyph unicode="&#xa7;" glyph-name="section" horiz-adv-x="672" d="M186 -2Q202 -18 242 -31T328 -44Q403 -44 440 -19T478 46Q478 80 454 104T395 144T294 186Q200 223 146 273T91 407Q91 490 164 542Q110 594 110 660Q110 708 139 745T223 802T348 822Q392
-822 429 815T509 795Q539 786 542 786L536 629H476L451 739Q444 747 414 756T344 765Q276 765 240 743T204 680Q204 643 225 619T274 580T369 539Q437 509 477 488T551 426T586 329Q586 243 513 182Q573 132 573 71Q573 27 547 -11T464 -74T323 -99Q272 -99 231
--90T137 -65Q102 -54 93 -53L104 117H169L186 -2ZM370 261Q375 259 406 246T465 215Q498 250 498 294Q498 348 455 382T322 453Q284 468 258 480T206 509Q189 493 181 476T172 435Q172 379 215 344T349 270L370 261Z" />
-<glyph unicode="&#xa8;" glyph-name="dieresis" horiz-adv-x="500" d="M104 665T89 683T73 728Q73 759 90 780T140 802Q168 802 184 784T200 738Q200 706 182 686T130 665Q104 665 89 683ZM331 665T316 683T300 728Q300 759 317 780T366 802Q395 802 411 783T427
-738Q427 706 409 686T356 665Q331 665 316 683Z" />
-<glyph unicode="&#xa9;" glyph-name="copyright" horiz-adv-x="1040" d="M95 607T151 705T305 860T520 917Q637 917 734 860T888 705T945 490Q945 373 889 275T735 119T520 61Q403 61 306 118T152 274T95 490Q95 607 151 705ZM154 388T202 302T335 164T520 113Q621
-113 705 164T837 301T885 490Q885 591 837 677T705 815T520 866Q418 866 334 815T202 678T154 490Q154 388 202 302ZM417 252T361 316T305 486Q305 554 337 610T425 698T552 731Q587 731 625 723T677 701V591H624L604 655Q581 673 522 673Q461 673 426 627T391
-502Q391 421 435 372T552 322Q584 322 612 334T660 366L683 326Q659 297 616 275T523 252Q417 252 361 316Z" />
-<glyph unicode="&#xaa;" glyph-name="ordfeminine" horiz-adv-x="518" d="M139 345T99 379T59 470Q59 542 130 577T346 618V635Q346 696 324 719T244 742Q206 742 166 730T94 703L68 752Q100 772 157 789T262 807Q351 807 394 770T438 645V401H494V358Q446 346
-406 346Q377 346 364 354T350 384V417Q325 387 286 366T197 345Q139 345 99 379ZM267 402T299 419T346 454V576Q246 574 202 550T157 476Q157 443 178 423T236 402Q267 402 299 419Z" />
-<glyph unicode="&#xab;" glyph-name="guillemotleft" horiz-adv-x="670" d="M324 520L167 299L324 86L274 52L56 264V333L274 551L324 520ZM604 520L433 299L604 86L553 52L322 264V333L553 551L604 520Z" />
-<glyph unicode="&#xac;" glyph-name="logicalnot" horiz-adv-x="688" d="M586 89H507V287H103V352H586V89Z" />
-<glyph unicode="&#xad;" glyph-name="uni00AD" horiz-adv-x="628" d="M516 284H112V357H516V284Z" />
-<glyph unicode="&#xae;" glyph-name="registered" horiz-adv-x="1040" d="M95 607T151 705T305 860T520 917Q637 917 734 860T888 705T945 490Q945 373 889 275T735 119T520 61Q403 61 306 118T152 274T95 490Q95 607 151 705ZM154 388T202 302T335 164T520 113Q621
-113 705 164T837 301T885 490Q885 591 837 677T705 815T520 866Q418 866 334 815T202 678T154 490Q154 388 202 302ZM371 669L326 679V723H405L476 724Q508 726 529 726Q617 726 663 694T709 603Q709 548 681 510T601 461Q632 447 647 425T677 367Q691 333 703
-317T744 299V253H669Q639 253 626 274T599 338Q587 381 573 407T528 444L450 445V303L501 293V253H326V293L371 305V669ZM466 497T531 497Q568 497 594 524T620 590Q620 637 595 657T516 677Q483 677 450 672V500Q466 497 531 497Z" />
-<glyph unicode="&#xaf;" glyph-name="overscore" horiz-adv-x="333" d="M303 697H28V768H303V697Z" />
-<glyph unicode="&#xb0;" glyph-name="degree" horiz-adv-x="463" d="M185 460T146 483T83 546T59 631Q59 679 82 718T145 779T231 802Q280 802 320 779T382 717T405 631Q405 583 382 544T319 483T231 460Q185 460 146 483ZM278 524T306 554T335 631Q335 675 305
-707T231 739Q186 739 157 708T128 631Q128 587 158 556T232 524Q278 524 306 554Z" />
-<glyph unicode="&#xb1;" glyph-name="plusminus" horiz-adv-x="661" d="M295 362L292 447V558H369V447L364 362L440 367H556V292H440L364 295L369 213V102H292V213L295 295L208 292H105V367H208L295 362ZM549 0H111V71H549V0Z" />
-<glyph unicode="&#xb2;" glyph-name="uni00B2" horiz-adv-x="498" d="M111 382T170 432T275 542T321 655Q321 699 296 726T224 753Q183 753 148 736T91 697L59 732Q82 762 132 789T244 817Q324 817 368 778T413 674Q413 602 335 514T151 362L368 377L405 452L454
-442L429 308H80L63 353Q111 382 170 432Z" />
-<glyph unicode="&#xb3;" glyph-name="uni00B3" horiz-adv-x="488" d="M182 307T143 314T75 336V389Q102 379 133 372T193 365Q350 365 350 463Q350 498 319 523T233 547Q219 541 174 526L158 574Q184 579 227 598Q309 637 309 694Q309 727 288 743T220 759Q185
-759 150 749T95 721L67 766Q92 790 140 805T245 821Q316 821 358 789T401 706Q401 664 374 632T287 574Q340 577 376 561T429 518T446 461Q446 392 386 350T214 307Q182 307 143 314Z" />
-<glyph unicode="&#xb4;" glyph-name="acute" horiz-adv-x="333" d="M102 686L264 884L336 821Q314 787 244 728T139 653L102 686Z" />
-<glyph unicode="&#xb5;" glyph-name="uni00B5" horiz-adv-x="683" d="M120 494L61 515V553L205 565L224 554V162Q224 142 237 118T278 77T343 60Q390 60 421 82T464 130V494L396 515L395 553L553 565L568 554V50H627V4Q609 -3 582 -8T528 -13Q480 -13 480 30V76Q462
-39 424 15T340 -10Q303 -10 270 3T217 41V-182H121L120 494Z" />
-<glyph unicode="&#xb6;" glyph-name="paragraph" horiz-adv-x="731" d="M266 397Q159 397 106 454T52 619Q52 682 83 731T174 807T321 835Q386 835 443 830Q509 826 558 826H663V775L578 765V58L651 48V0H488V764Q419 770 379 770L356 769V0H168V48L266 58V397Z" />
-<glyph unicode="&#xb7;" glyph-name="middot" horiz-adv-x="175" d="M56 314T37 332T18 378Q18 409 40 430T93 451Q124 451 140 433T157 387Q157 355 135 335T82 314Q56 314 37 332Z" />
-<glyph unicode="&#xb8;" glyph-name="cedilla" horiz-adv-x="300" d="M60 -241T40 -237T6 -228L7 -159Q17 -163 30 -165T52 -167Q92 -167 109 -154T126 -96Q126 -70 115 -42T92 1L123 6L142 1Q163 -18 185 -57T207 -137Q207 -193 175 -217T77 -241Q60 -241 40 -237Z" />
-<glyph unicode="&#xb9;" glyph-name="uni00B9" horiz-adv-x="484" d="M221 724Q179 707 93 690L80 742Q133 758 175 776T255 823H257L308 813V366L420 356V308H93V356L221 366V724Z" />
-<glyph unicode="&#xba;" glyph-name="ordmasculine" horiz-adv-x="515" d="M164 345T107 403T49 572Q49 647 80 698T161 775T263 800Q359 800 412 743T466 578Q466 499 435 447T356 370T256 345Q164 345 107 403ZM292 393T316 407T353 459T366 566Q366 654 339
-703T260 752Q209 752 180 711T150 581Q150 493 180 443T255 393Q292 393 316 407Z" />
-<glyph unicode="&#xbb;" glyph-name="guillemotright" horiz-adv-x="670" d="M348 333V264L116 52L66 86L237 299L66 520L116 551L348 333ZM614 333V264L397 52L346 86L503 299L346 520L397 551L614 333Z" />
-<glyph unicode="&#xbc;" glyph-name="onequarter" horiz-adv-x="1177" d="M221 674Q179 657 93 640L80 692Q133 708 175 726T255 773H257L308 763V316L420 306V258H93V306L221 316V674ZM794 807L433 -77L362 -73L725 813L794 807ZM716 171Q767 262 827 370T918
-534H999L1015 515L821 200L782 148L975 156L984 291L1056 296V160L1146 165V99H1056V0H974V99H728L698 138L716 171Z" />
-<glyph unicode="&#xbd;" glyph-name="onehalf" horiz-adv-x="1170" d="M221 674Q179 657 93 640L80 692Q133 708 175 726T255 773H257L308 763V316L420 306V258H93V306L221 316V674ZM794 807L433 -77L362 -73L725 813L794 807ZM783 65T842 115T947 225T993 338Q993
-382 968 409T896 436Q855 436 820 419T763 380L731 415Q754 445 804 472T916 500Q996 500 1040 461T1085 357Q1085 285 1007 197T823 45L1040 60L1077 135L1126 125L1101 -9H752L735 36Q783 65 842 115Z" />
-<glyph unicode="&#xbe;" glyph-name="threequarters" horiz-adv-x="1181" d="M182 257T143 264T75 286V339Q102 329 133 322T193 315Q350 315 350 413Q350 448 319 473T233 497Q219 491 174 476L158 524Q184 529 227 548Q309 587 309 644Q309 677 288 693T220
-709Q185 709 150 699T95 671L67 716Q92 740 140 755T245 771Q316 771 358 739T401 656Q401 614 374 582T287 524Q340 527 376 511T429 468T446 411Q446 342 386 300T214 257Q182 257 143 264ZM798 807L437 -77L366 -73L729 813L798 807ZM720 171Q771 262 831 370T922
-534H1003L1019 515L825 200L786 148L979 156L988 291L1060 296V160L1150 165V99H1060V0H978V99H732L702 138L720 171Z" />
-<glyph unicode="&#xbf;" glyph-name="questiondown" horiz-adv-x="487" d="M328 703T347 686T366 641Q366 610 343 589T291 568Q259 568 242 586T225 631Q225 664 247 683T302 703Q328 703 347 686ZM342 388T348 314Q348 275 319 246T231 179Q194 155 172 138T134
-100Q132 90 130 71T128 36Q128 -10 154 -50T232 -116T354 -141Q398 -141 429 -127L445 -189Q428 -199 394 -206T323 -213Q177 -213 106 -145T35 31Q35 78 54 114T100 174T170 230Q201 252 219 267T246 300Q248 308 248 314L247 326Q247 415 243 452H313Q342 388
-348 314Z" />
-<glyph unicode="&#xc0;" glyph-name="Agrave" horiz-adv-x="692" d="M290 749H400L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49L49 59L290 749ZM353 589L328 677L304 587L203 266H458L353 589ZM330 817T279 856T201 930L281 981L416 829L368
-799Q330 817 279 856Z" />
-<glyph unicode="&#xc1;" glyph-name="Aacute" horiz-adv-x="692" d="M290 749H400L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49L49 59L290 749ZM353 589L328 677L304 587L203 266H458L353 589ZM268 829L402 981L483 930Q455 895 406 856T318
-799L268 829Z" />
-<glyph unicode="&#xc2;" glyph-name="Acircumflex" horiz-adv-x="692" d="M290 749H400L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49L49 59L290 749ZM353 589L328 677L304 587L203 266H458L353 589ZM384 982L519 838L478 809L344 912L208
-809L169 837L304 982H384Z" />
-<glyph unicode="&#xc3;" glyph-name="Atilde" horiz-adv-x="692" d="M290 749H400L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49L49 59L290 749ZM353 589L328 677L304 587L203 266H458L353 589ZM390 815T371 825T327 856Q310 871 298 878T270
-886Q245 886 233 871T210 827L163 854Q177 899 205 927T276 955Q307 955 326 944T370 911Q387 896 398 889T422 882Q444 882 457 899T481 943L528 916Q513 869 488 842T419 815Q390 815 371 825Z" />
-<glyph unicode="&#xc4;" glyph-name="Adieresis" horiz-adv-x="692" d="M290 749H400L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49L49 59L290 749ZM353 589L328 677L304 587L203 266H458L353 589ZM188 819T173 837T158 882Q158 914 174
-935T223 956H224Q252 956 268 937T284 892Q284 860 266 840T214 819H213Q188 819 173 837ZM433 819T418 837T402 882Q402 913 419 934T467 956H468Q496 956 511 937T527 892Q527 860 510 840T458 819Q433 819 418 837Z" />
-<glyph unicode="&#xc5;" glyph-name="Aring" horiz-adv-x="692" d="M-13 49L49 59L287 741Q234 752 208 782T181 856Q181 917 229 950T347 983Q424 983 465 950T506 861Q506 815 478 785T402 743L643 59L705 49V0H441V49L524 59L477 207H185L138 59L224 49V0H-13V49ZM252
-826T275 803T344 779Q434 779 434 855Q434 892 413 915T345 938Q299 938 276 919T252 861Q252 826 275 803ZM458 266L353 589L328 677L304 587L203 266H458Z" />
-<glyph unicode="&#xc6;" glyph-name="AE" horiz-adv-x="921" d="M401 216H142L79 59L156 48V0H-88V48L-15 59L260 682L127 694V743H826L842 585H785L754 687L508 692V409L672 412L685 495H741V265H685L672 352L508 354V55L789 66L849 192L910 175L873 0H315V48L401
-59V216ZM401 688H335L280 557L166 275H401V688Z" />
-<glyph unicode="&#xc7;" glyph-name="Ccedilla" horiz-adv-x="653" d="M268 -11T191 36T73 170T33 372Q33 484 80 570T209 703T393 751Q470 751 578 727L611 721L601 541H534L509 668Q495 680 461 688T376 697Q312 697 262 661T184 553T155 383Q155 289 180 212T256
-90T382 44Q435 44 463 53T512 79L554 177L617 169L593 27Q572 26 531 13Q495 2 462 -4T378 -11Q268 -11 191 36ZM308 -241T288 -237T254 -228L255 -159Q265 -163 278 -165T300 -167Q340 -167 357 -154T374 -96Q374 -70 363 -42T340 1L371 6L390 1Q411 -18 433 -57T455
--137Q455 -193 423 -217T325 -241Q308 -241 288 -237Z" />
-<glyph unicode="&#xc8;" glyph-name="Egrave" horiz-adv-x="651" d="M129 681L47 693V743H556L570 588H513L484 685L236 691V409L403 412L417 495H472V265H417L403 351L236 354V56L518 66L571 192L630 174L601 0H46V49L129 59V681ZM328 817T277 856T199 930L279
-981L414 829L366 799Q328 817 277 856Z" />
-<glyph unicode="&#xc9;" glyph-name="Eacute" horiz-adv-x="651" d="M129 681L47 693V743H556L570 588H513L484 685L236 691V409L403 412L417 495H472V265H417L403 351L236 354V56L518 66L571 192L630 174L601 0H46V49L129 59V681ZM266 829L400 981L481 930Q453
-895 404 856T316 799L266 829Z" />
-<glyph unicode="&#xca;" glyph-name="Ecircumflex" horiz-adv-x="651" d="M129 681L47 693V743H556L570 588H513L484 685L236 691V409L403 412L417 495H472V265H417L403 351L236 354V56L518 66L571 192L630 174L601 0H46V49L129 59V681ZM382 982L517 838L476 809L342
-912L206 809L167 837L302 982H382Z" />
-<glyph unicode="&#xcb;" glyph-name="Edieresis" horiz-adv-x="651" d="M129 681L47 693V743H556L570 588H513L484 685L236 691V409L403 412L417 495H472V265H417L403 351L236 354V56L518 66L571 192L630 174L601 0H46V49L129 59V681ZM186 819T171 837T156 882Q156
-914 172 935T221 956H222Q250 956 266 937T282 892Q282 860 264 840T212 819H211Q186 819 171 837ZM431 819T416 837T400 882Q400 913 417 934T465 956H466Q494 956 509 937T525 892Q525 860 508 840T456 819Q431 819 416 837Z" />
-<glyph unicode="&#xcc;" glyph-name="Igrave" horiz-adv-x="403" d="M147 681L54 693V743H348V693L255 681V59L348 48V0H55V49L147 59V681ZM189 817T138 856T60 930L140 981L275 829L227 799Q189 817 138 856Z" />
-<glyph unicode="&#xcd;" glyph-name="Iacute" horiz-adv-x="403" d="M147 681L54 693V743H348V693L255 681V59L348 48V0H55V49L147 59V681ZM127 829L261 981L342 930Q314 895 265 856T177 799L127 829Z" />
-<glyph unicode="&#xce;" glyph-name="Icircumflex" horiz-adv-x="403" d="M147 681L54 693V743H348V693L255 681V59L348 48V0H55V49L147 59V681ZM243 982L378 838L337 809L203 912L67 809L28 837L163 982H243Z" />
-<glyph unicode="&#xcf;" glyph-name="Idieresis" horiz-adv-x="403" d="M147 681L54 693V743H348V693L255 681V59L348 48V0H55V49L147 59V681ZM47 819T32 837T17 882Q17 914 33 935T82 956H83Q111 956 127 937T143 892Q143 860 125 840T73 819H72Q47 819 32 837ZM292
-819T277 837T261 882Q261 913 278 934T326 956H327Q355 956 370 937T386 892Q386 860 369 840T317 819Q292 819 277 837Z" />
-<glyph unicode="&#xd0;" glyph-name="Eth" horiz-adv-x="758" d="M129 681L51 693V743H182Q213 743 271 747Q329 751 358 751Q544 751 634 658T725 395Q725 277 679 186T548 43T355 -8Q331 -8 273 -4Q213 0 183 0H46V49L129 59V361H54V413H129V681ZM410 361H235V56Q270
-48 325 48H355Q430 49 487 86T577 196T609 375Q609 533 541 615T334 697Q305 697 265 693Q248 690 235 690V413H410V361Z" />
-<glyph unicode="&#xd1;" glyph-name="Ntilde" horiz-adv-x="799" d="M130 681L50 693V743H236L569 255L625 149V681L538 693V743H774V693L694 681V0H615L275 499L198 631V59L293 49V0H50V49L130 60V681ZM459 815T440 825T396 856Q379 871 367 878T339 886Q314
-886 302 871T279 827L232 854Q246 899 274 927T345 955Q376 955 395 944T439 911Q456 896 467 889T491 882Q513 882 526 899T550 943L597 916Q582 869 557 842T488 815Q459 815 440 825Z" />
-<glyph unicode="&#xd2;" glyph-name="Ograve" horiz-adv-x="722" d="M247 -11T177 36T70 168T34 367Q34 482 77 569T197 703T368 751Q524 751 606 653T689 380Q689 263 645 175T523 38T349 -11Q247 -11 177 36ZM265 699T209 615T153 367Q153 217 207 130T360 42Q456
-42 512 129T569 379Q569 530 515 614T362 699Q265 699 209 615ZM350 817T299 856T221 930L301 981L436 829L388 799Q350 817 299 856Z" />
-<glyph unicode="&#xd3;" glyph-name="Oacute" horiz-adv-x="722" d="M247 -11T177 36T70 168T34 367Q34 482 77 569T197 703T368 751Q524 751 606 653T689 380Q689 263 645 175T523 38T349 -11Q247 -11 177 36ZM265 699T209 615T153 367Q153 217 207 130T360 42Q456
-42 512 129T569 379Q569 530 515 614T362 699Q265 699 209 615ZM288 829L422 981L503 930Q475 895 426 856T338 799L288 829Z" />
-<glyph unicode="&#xd4;" glyph-name="Ocircumflex" horiz-adv-x="722" d="M247 -11T177 36T70 168T34 367Q34 482 77 569T197 703T368 751Q524 751 606 653T689 380Q689 263 645 175T523 38T349 -11Q247 -11 177 36ZM265 699T209 615T153 367Q153 217 207 130T360
-42Q456 42 512 129T569 379Q569 530 515 614T362 699Q265 699 209 615ZM404 982L539 838L498 809L364 912L228 809L189 837L324 982H404Z" />
-<glyph unicode="&#xd5;" glyph-name="Otilde" horiz-adv-x="722" d="M247 -11T177 36T70 168T34 367Q34 482 77 569T197 703T368 751Q524 751 606 653T689 380Q689 263 645 175T523 38T349 -11Q247 -11 177 36ZM265 699T209 615T153 367Q153 217 207 130T360 42Q456
-42 512 129T569 379Q569 530 515 614T362 699Q265 699 209 615ZM410 815T391 825T347 856Q330 871 318 878T290 886Q265 886 253 871T230 827L183 854Q197 899 225 927T296 955Q327 955 346 944T390 911Q407 896 418 889T442 882Q464 882 477 899T501 943L548 916Q533
-869 508 842T439 815Q410 815 391 825Z" />
-<glyph unicode="&#xd6;" glyph-name="Odieresis" horiz-adv-x="722" d="M247 -11T177 36T70 168T34 367Q34 482 77 569T197 703T368 751Q524 751 606 653T689 380Q689 263 645 175T523 38T349 -11Q247 -11 177 36ZM265 699T209 615T153 367Q153 217 207 130T360
-42Q456 42 512 129T569 379Q569 530 515 614T362 699Q265 699 209 615ZM208 819T193 837T178 882Q178 914 194 935T243 956H244Q272 956 288 937T304 892Q304 860 286 840T234 819H233Q208 819 193 837ZM453 819T438 837T422 882Q422 913 439 934T487 956H488Q516
-956 531 937T547 892Q547 860 530 840T478 819Q453 819 438 837Z" />
-<glyph unicode="&#xd7;" glyph-name="multiply" horiz-adv-x="609" d="M84 464L143 525L305 352L466 525L525 464L356 301L525 138L466 77L305 250L143 77L84 138L254 301L84 464Z" />
-<glyph unicode="&#xd8;" glyph-name="Oslash" horiz-adv-x="723" d="M119 65T77 154T34 367Q34 482 77 569T197 703T368 751Q427 751 478 736L518 839L565 823L523 718Q605 677 647 590T689 380Q689 263 645 175T522 38T346 -11Q298 -11 246 4L201 -104L152 -88L200
-23Q119 65 77 154ZM266 699T210 615T153 367Q153 279 174 211T237 103L453 674Q414 699 363 699Q266 699 210 615ZM570 466T549 533T486 640L270 69Q309 42 361 42Q424 42 471 80T544 194T570 379Q570 466 549 533Z" />
-<glyph unicode="&#xd9;" glyph-name="Ugrave" horiz-adv-x="740" d="M234 -8T165 70T95 314V681L24 693V743H291V693L206 680V303Q206 167 254 107T394 47Q485 47 530 111T576 297V680L492 693V743H725V693L652 681V302Q652 146 578 69T381 -8Q234 -8 165 70ZM378
-817T327 856T249 930L329 981L464 829L416 799Q378 817 327 856Z" />
-<glyph unicode="&#xda;" glyph-name="Uacute" horiz-adv-x="740" d="M234 -8T165 70T95 314V681L24 693V743H291V693L206 680V303Q206 167 254 107T394 47Q485 47 530 111T576 297V680L492 693V743H725V693L652 681V302Q652 146 578 69T381 -8Q234 -8 165 70ZM316
-829L450 981L531 930Q503 895 454 856T366 799L316 829Z" />
-<glyph unicode="&#xdb;" glyph-name="Ucircumflex" horiz-adv-x="740" d="M234 -8T165 70T95 314V681L24 693V743H291V693L206 680V303Q206 167 254 107T394 47Q485 47 530 111T576 297V680L492 693V743H725V693L652 681V302Q652 146 578 69T381 -8Q234 -8 165
-70ZM432 982L567 838L526 809L392 912L256 809L217 837L352 982H432Z" />
-<glyph unicode="&#xdc;" glyph-name="Udieresis" horiz-adv-x="740" d="M234 -8T165 70T95 314V681L24 693V743H291V693L206 680V303Q206 167 254 107T394 47Q485 47 530 111T576 297V680L492 693V743H725V693L652 681V302Q652 146 578 69T381 -8Q234 -8 165 70ZM236
-819T221 837T206 882Q206 914 222 935T271 956H272Q300 956 316 937T332 892Q332 860 314 840T262 819H261Q236 819 221 837ZM481 819T466 837T450 882Q450 913 467 934T515 956H516Q544 956 559 937T575 892Q575 860 558 840T506 819Q481 819 466 837Z" />
-<glyph unicode="&#xdd;" glyph-name="Yacute" horiz-adv-x="644" d="M273 289L48 680L-12 693V743H249V693L170 681L311 413L343 337L379 413L512 681L430 693V743H658V693L593 681L384 290V60L496 49V0H164V49L273 59V289ZM254 829L388 981L469 930Q441 895 392
-856T304 799L254 829Z" />
-<glyph unicode="&#xde;" glyph-name="Thorn" horiz-adv-x="645" d="M128 681L46 694V744H322L323 694L235 681V571L268 574Q278 575 316 578T390 581Q499 581 558 532T617 384Q617 273 549 218T358 162Q283 162 235 167V59L342 48V0H45V48L128 59V681ZM416 213T458
-253T501 378Q501 448 464 487T347 526Q298 526 235 517V217Q269 213 304 213T346 213Q416 213 458 253Z" />
-<glyph unicode="&#xdf;" glyph-name="germandbls" horiz-adv-x="635" d="M91 466Q91 564 129 636T231 746T375 784Q454 784 501 751T549 651Q549 609 533 582T484 522Q460 498 449 481T437 442Q437 417 454 396T507 345Q541 315 562 293T598 238T614 165Q614 80
-552 35T386 -11Q368 -11 343 -8T302 0V71Q345 54 393 54Q447 54 474 79T502 145Q502 186 482 214T422 280Q383 316 363 345T343 413Q343 437 354 456T389 504Q417 537 432 564T447 628Q447 726 352 726Q279 726 238 664T197 482V0H25V49L91 58V466Z" />
-<glyph unicode="&#xe0;" glyph-name="agrave" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486 -5T432
--10Q404 -10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73ZM282 661T240 693T159 762T107 821L179 884L340 686L303 653H302Q282 661
-240 693Z" />
-<glyph unicode="&#xe1;" glyph-name="aacute" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486 -5T432
--10Q404 -10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73ZM195 686L355 885L431 821Q410 787 341 728T234 653L195 686Z" />
-<glyph unicode="&#xe2;" glyph-name="acircumflex" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486
--5T432 -10Q404 -10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73ZM313 860L453 665L413 637L273 781L128 637L90 664L233 860H313Z"
-/>
-<glyph unicode="&#xe3;" glyph-name="atilde" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486 -5T432
--10Q404 -10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73ZM91 744T122 774T202 805Q232 805 252 793T298 758Q317 741 328 734T354
-726Q381 726 395 745T415 785L466 760Q455 714 426 684T350 654Q321 654 302 665T257 700Q238 717 226 725T198 733Q173 733 160 720T139 693T128 673L81 700Q91 744 122 774Z" />
-<glyph unicode="&#xe4;" glyph-name="adieresis" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486 -5T432
--10Q404 -10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73ZM128 657T113 675T97 720Q97 751 114 772T163 794Q191 794 207 775T223
-730Q223 698 206 678T155 657Q128 657 113 675ZM355 657T340 675T324 720Q324 751 341 772T390 794Q418 794 433 775T449 730Q449 698 432 678T380 657Q355 657 340 675Z" />
-<glyph unicode="&#xe5;" glyph-name="aring" horiz-adv-x="561" d="M45 244T139 288T377 336V364Q377 411 367 438T333 477T263 490Q212 490 172 476T91 440L66 492Q79 503 114 521T195 553T287 567Q358 567 399 548T459 485T477 370V49H536V5Q516 0 486 -5T432
--10Q404 -10 394 -2T384 36V69Q354 39 311 14T212 -11Q140 -11 93 30T45 150Q45 244 139 288ZM281 57T315 73T377 111V283Q268 283 213 250T157 162Q157 108 183 83T255 57Q281 57 315 73ZM192 640T151 678T110 778Q110 820 134 850T197 897T279 913Q353 913 394
-876T435 779Q435 715 388 678T272 640Q192 640 151 678ZM365 687T365 773Q365 814 343 839T275 865Q230 865 205 843T180 780Q180 740 204 714T274 687Q365 687 365 773Z" />
-<glyph unicode="&#xe6;" glyph-name="ae" horiz-adv-x="869" d="M138 -11T90 29T41 148Q41 242 134 287T370 336Q370 403 362 435T331 479T259 492Q209 492 168 478T80 439L55 490Q69 503 106 521T191 553T285 567Q351 567 390 550T447 493Q482 530 528 550T629
-570Q723 570 774 519T829 371Q829 310 822 278H477Q479 179 523 119T648 58Q688 58 731 72T799 106L818 63Q789 33 733 11T618 -11Q547 -11 496 17T413 96Q384 54 331 22T210 -11Q138 -11 90 29ZM719 331Q720 344 720 374Q720 439 694 476T611 514Q553 514 518
-472T478 331H719ZM296 57T335 82T392 139Q369 204 369 287Q264 286 210 251T155 161Q155 107 181 82T253 57Q296 57 335 82Z" />
-<glyph unicode="&#xe7;" glyph-name="ccedilla" horiz-adv-x="513" d="M33 357T65 424T161 530T314 570Q357 570 388 562T462 540L458 386H393L371 488Q365 516 295 516Q225 516 185 460T144 299Q144 181 189 120T308 58Q350 58 387 71T452 102L471 62Q445 35
-397 14T299 -10Q320 -34 336 -67T353 -136Q353 -192 321 -216T223 -241Q206 -241 186 -237T152 -228L153 -159Q163 -163 176 -165T198 -167Q238 -167 255 -154T272 -96Q272 -56 244 -8Q141 5 87 82T33 274Q33 357 65 424Z" />
-<glyph unicode="&#xe8;" glyph-name="egrave" horiz-adv-x="544" d="M170 -11T107 68T43 279Q43 366 76 432T168 534T304 570Q397 570 448 519T503 371Q503 310 496 278H152Q154 179 198 119T323 58Q363 58 406 72T474 107L493 63Q464 33 407 11T291 -11Q170 -11
-107 68ZM393 331Q396 352 396 374Q395 439 369 476T285 514Q227 514 193 472T153 331H393ZM301 661T259 693T178 762T126 821L198 884L359 686L322 653H321Q301 661 259 693Z" />
-<glyph unicode="&#xe9;" glyph-name="eacute" horiz-adv-x="544" d="M170 -11T107 68T43 279Q43 366 76 432T168 534T304 570Q397 570 448 519T503 371Q503 310 496 278H152Q154 179 198 119T323 58Q363 58 406 72T474 107L493 63Q464 33 407 11T291 -11Q170 -11
-107 68ZM393 331Q396 352 396 374Q395 439 369 476T285 514Q227 514 193 472T153 331H393ZM214 686L374 885L450 821Q429 787 360 728T253 653L214 686Z" />
-<glyph unicode="&#xea;" glyph-name="ecircumflex" horiz-adv-x="544" d="M170 -11T107 68T43 279Q43 366 76 432T168 534T304 570Q397 570 448 519T503 371Q503 310 496 278H152Q154 179 198 119T323 58Q363 58 406 72T474 107L493 63Q464 33 407 11T291 -11Q170
--11 107 68ZM393 331Q396 352 396 374Q395 439 369 476T285 514Q227 514 193 472T153 331H393ZM332 860L472 665L432 637L292 781L147 637L109 664L252 860H332Z" />
-<glyph unicode="&#xeb;" glyph-name="edieresis" horiz-adv-x="544" d="M170 -11T107 68T43 279Q43 366 76 432T168 534T304 570Q397 570 448 519T503 371Q503 310 496 278H152Q154 179 198 119T323 58Q363 58 406 72T474 107L493 63Q464 33 407 11T291 -11Q170
--11 107 68ZM393 331Q396 352 396 374Q395 439 369 476T285 514Q227 514 193 472T153 331H393ZM147 657T132 675T116 720Q116 751 133 772T182 794Q210 794 226 775T242 730Q242 698 225 678T174 657Q147 657 132 675ZM374 657T359 675T343 720Q343 751 360 772T409
-794Q437 794 452 775T468 730Q468 698 451 678T399 657Q374 657 359 675Z" />
-<glyph unicode="&#xec;" glyph-name="igrave" horiz-adv-x="333" d="M123 478L47 496V549L202 568H204L227 550V57L307 49V0H42V49L123 58V478ZM176 661T134 693T53 762T1 821L73 884L234 686L197 653H196Q176 661 134 693Z" />
-<glyph unicode="&#xed;" glyph-name="iacute" horiz-adv-x="333" d="M123 478L47 496V549L202 568H204L227 550V57L307 49V0H42V49L123 58V478ZM89 686L249 885L325 821Q304 787 235 728T128 653L89 686Z" />
-<glyph unicode="&#xee;" glyph-name="icircumflex" horiz-adv-x="333" d="M123 478L47 496V549L202 568H204L227 550V57L307 49V0H42V49L123 58V478ZM207 860L347 665L307 637L167 781L22 637L-16 664L127 860H207Z" />
-<glyph unicode="&#xef;" glyph-name="idieresis" horiz-adv-x="333" d="M123 478L47 496V549L202 568H204L227 550V57L307 49V0H42V49L123 58V478ZM22 657T7 675T-9 720Q-9 751 8 772T57 794Q85 794 101 775T117 730Q117 698 100 678T49 657Q22 657 7 675ZM249
-657T234 675T218 720Q218 751 235 772T284 794Q312 794 327 775T343 730Q343 698 326 678T274 657Q249 657 234 675Z" />
-<glyph unicode="&#xf0;" glyph-name="eth" horiz-adv-x="581" d="M167 -11T103 63T39 261Q39 360 74 430T169 535T296 570Q352 570 394 550Q372 606 331 658T234 746L165 660L117 693L190 777Q163 794 133 809T82 829L102 878Q168 858 231 826L295 904L340 868L280
-797Q402 714 472 596T543 325Q543 237 518 161T436 37T292 -11Q167 -11 103 63ZM431 43T431 315Q431 366 425 407T410 473Q397 490 369 505T299 520Q232 520 193 455T153 271Q153 172 187 108T295 43Q431 43 431 315Z" />
-<glyph unicode="&#xf1;" glyph-name="ntilde" horiz-adv-x="664" d="M105 478L33 496V550L176 568H179L200 550V508L199 484Q235 516 294 542T407 568Q470 568 504 544T553 471T567 337V57L637 50V0H400V49L462 57V338Q462 397 454 430T424 480T360 497Q324 497
-283 479T210 437V58L278 49V0H42V49L105 58V478ZM137 744T168 774T248 805Q278 805 298 793T344 758Q363 741 374 734T400 726Q427 726 441 745T461 785L512 760Q501 714 472 684T396 654Q367 654 348 665T303 700Q284 717 272 725T244 733Q219 733 206 720T185
-693T174 673L127 700Q137 744 168 774Z" />
-<glyph unicode="&#xf2;" glyph-name="ograve" horiz-adv-x="608" d="M45 369T82 435T179 535T309 570Q435 570 498 490T562 280Q562 189 525 123T428 23T298 -11Q172 -11 109 69T45 279Q45 369 82 435ZM373 46T410 103T447 272Q447 383 413 448T304 513Q235 513
-198 456T160 287Q160 176 195 111T304 46Q373 46 410 103ZM314 661T272 693T191 762T139 821L211 884L372 686L335 653H334Q314 661 272 693Z" />
-<glyph unicode="&#xf3;" glyph-name="oacute" horiz-adv-x="608" d="M45 369T82 435T179 535T309 570Q435 570 498 490T562 280Q562 189 525 123T428 23T298 -11Q172 -11 109 69T45 279Q45 369 82 435ZM373 46T410 103T447 272Q447 383 413 448T304 513Q235 513
-198 456T160 287Q160 176 195 111T304 46Q373 46 410 103ZM227 686L387 885L463 821Q442 787 373 728T266 653L227 686Z" />
-<glyph unicode="&#xf4;" glyph-name="ocircumflex" horiz-adv-x="608" d="M45 369T82 435T179 535T309 570Q435 570 498 490T562 280Q562 189 525 123T428 23T298 -11Q172 -11 109 69T45 279Q45 369 82 435ZM373 46T410 103T447 272Q447 383 413 448T304 513Q235
-513 198 456T160 287Q160 176 195 111T304 46Q373 46 410 103ZM345 860L485 665L445 637L305 781L160 637L122 664L265 860H345Z" />
-<glyph unicode="&#xf5;" glyph-name="otilde" horiz-adv-x="608" d="M45 369T82 435T179 535T309 570Q435 570 498 490T562 280Q562 189 525 123T428 23T298 -11Q172 -11 109 69T45 279Q45 369 82 435ZM373 46T410 103T447 272Q447 383 413 448T304 513Q235 513
-198 456T160 287Q160 176 195 111T304 46Q373 46 410 103ZM123 744T154 774T234 805Q264 805 284 793T330 758Q349 741 360 734T386 726Q413 726 427 745T447 785L498 760Q487 714 458 684T382 654Q353 654 334 665T289 700Q270 717 258 725T230 733Q205 733 192
-720T171 693T160 673L113 700Q123 744 154 774Z" />
-<glyph unicode="&#xf6;" glyph-name="odieresis" horiz-adv-x="608" d="M45 369T82 435T179 535T309 570Q435 570 498 490T562 280Q562 189 525 123T428 23T298 -11Q172 -11 109 69T45 279Q45 369 82 435ZM373 46T410 103T447 272Q447 383 413 448T304 513Q235
-513 198 456T160 287Q160 176 195 111T304 46Q373 46 410 103ZM160 657T145 675T129 720Q129 751 146 772T195 794Q223 794 239 775T255 730Q255 698 238 678T187 657Q160 657 145 675ZM387 657T372 675T356 720Q356 751 373 772T422 794Q450 794 465 775T481 730Q481
-698 464 678T412 657Q387 657 372 675Z" />
-<glyph unicode="&#xf7;" glyph-name="divide" horiz-adv-x="665" d="M310 462T292 479T273 523Q273 552 295 572T346 593Q377 593 393 576T409 531Q409 500 388 481T335 462Q310 462 292 479ZM560 285H105V357H560V285ZM264 142T286 162T338 183Q369 183 385 166T401
-122Q401 91 379 72T327 52Q302 52 283 69T264 113Q264 142 286 162Z" />
-<glyph unicode="&#xf8;" glyph-name="oslash" horiz-adv-x="600" d="M41 369T78 435T175 535T305 570Q346 570 379 561L414 657L457 646L424 546Q491 513 524 444T558 280Q558 189 521 123T424 23T294 -11Q257 -11 223 -3L184 -106L138 -93L177 12Q109 45 75 115T41
-279Q41 369 78 435ZM156 222T170 171T212 90L359 498Q335 513 300 513Q231 513 194 456T156 287Q156 222 170 171ZM369 46T406 103T443 272Q443 407 389 467L241 61Q267 46 300 46Q369 46 406 103Z" />
-<glyph unicode="&#xf9;" glyph-name="ugrave" horiz-adv-x="632" d="M472 -9T459 2T445 38V72Q412 39 363 14T263 -11Q170 -11 131 39T92 204V494L36 510V554L176 567H177L196 555V212Q196 154 204 122T234 74T297 58Q337 58 372 75T433 115V494L361 510V554L513
-567H514L537 555V51H597L596 6Q568 -1 548 -5T500 -9Q472 -9 459 2ZM312 661T270 693T189 762T137 821L209 884L370 686L333 653H332Q312 661 270 693Z" />
-<glyph unicode="&#xfa;" glyph-name="uacute" horiz-adv-x="632" d="M472 -9T459 2T445 38V72Q412 39 363 14T263 -11Q170 -11 131 39T92 204V494L36 510V554L176 567H177L196 555V212Q196 154 204 122T234 74T297 58Q337 58 372 75T433 115V494L361 510V554L513
-567H514L537 555V51H597L596 6Q568 -1 548 -5T500 -9Q472 -9 459 2ZM225 686L385 885L461 821Q440 787 371 728T264 653L225 686Z" />
-<glyph unicode="&#xfb;" glyph-name="ucircumflex" horiz-adv-x="632" d="M472 -9T459 2T445 38V72Q412 39 363 14T263 -11Q170 -11 131 39T92 204V494L36 510V554L176 567H177L196 555V212Q196 154 204 122T234 74T297 58Q337 58 372 75T433 115V494L361 510V554L513
-567H514L537 555V51H597L596 6Q568 -1 548 -5T500 -9Q472 -9 459 2ZM343 860L483 665L443 637L303 781L158 637L120 664L263 860H343Z" />
-<glyph unicode="&#xfc;" glyph-name="udieresis" horiz-adv-x="632" d="M472 -9T459 2T445 38V72Q412 39 363 14T263 -11Q170 -11 131 39T92 204V494L36 510V554L176 567H177L196 555V212Q196 154 204 122T234 74T297 58Q337 58 372 75T433 115V494L361 510V554L513
-567H514L537 555V51H597L596 6Q568 -1 548 -5T500 -9Q472 -9 459 2ZM158 657T143 675T127 720Q127 751 144 772T193 794Q221 794 237 775T253 730Q253 698 236 678T185 657Q158 657 143 675ZM385 657T370 675T354 720Q354 751 371 772T420 794Q448 794 463 775T479
-730Q479 698 462 678T410 657Q385 657 370 675Z" />
-<glyph unicode="&#xfd;" glyph-name="yacute" horiz-adv-x="572" d="M109 -249T93 -247T69 -241V-154Q75 -158 92 -160T126 -162Q174 -162 210 -129T281 0H233L43 495L-3 508V555H238V508L161 496L259 201L305 55L348 202L437 496L370 508V555H571V508L521 496Q374
-46 348 -15Q314 -101 286 -149T220 -223T126 -249Q109 -249 93 -247ZM222 686L382 885L458 821Q437 787 368 728T261 653L222 686Z" />
-<glyph unicode="&#xfe;" glyph-name="thorn" horiz-adv-x="608" d="M160 819H162L185 804V503Q213 531 255 550T348 570Q408 570 457 541T536 451T566 297Q566 211 531 141T430 30T277 -11Q231 -11 182 -2L184 -66L185 -185L294 -197V-242H8V-197L81 -185V747L-1
-758V800L160 819ZM270 499T237 481T185 442V74Q191 60 219 52T283 43Q361 43 407 105T454 290Q454 395 413 447T307 499Q270 499 237 481Z" />
-<glyph unicode="&#xff;" glyph-name="ydieresis" horiz-adv-x="572" d="M109 -249T93 -247T69 -241V-154Q75 -158 92 -160T126 -162Q174 -162 210 -129T281 0H233L43 495L-3 508V555H238V508L161 496L259 201L305 55L348 202L437 496L370 508V555H571V508L521
-496Q374 46 348 -15Q314 -101 286 -149T220 -223T126 -249Q109 -249 93 -247ZM155 657T140 675T124 720Q124 751 141 772T190 794Q218 794 234 775T250 730Q250 698 233 678T182 657Q155 657 140 675ZM382 657T367 675T351 720Q351 751 368 772T417 794Q445 794
-460 775T476 730Q476 698 459 678T407 657Q382 657 367 675Z" />
-<glyph unicode="&#x2013;" glyph-name="endash" horiz-adv-x="814" d="M701 283H112V357H701V283Z" />
-<glyph unicode="&#x2014;" glyph-name="emdash" horiz-adv-x="1185" d="M1073 283H112V357H1073V283Z" />
-<glyph unicode="&#x2018;" glyph-name="quoteleft" horiz-adv-x="381" d="M183 430T160 453T124 514T110 595Q110 656 131 709T182 798T238 847L265 820V809Q252 799 236 771T208 703T196 619Q196 598 204 583T230 548Q246 530 254 517T262 485Q262 459 247 445T208
-430Q183 430 160 453Z" />
-<glyph unicode="&#x2019;" glyph-name="quoteright" horiz-adv-x="381" d="M115 448V459Q127 469 144 503T173 583T185 673Q185 684 179 693T157 717Q139 734 129 748T119 783Q119 809 133 824T172 839Q198 839 221 820T257 768T271 692Q271 631 250 574T198 475T143
-421L115 448Z" />
-<glyph unicode="&#x201a;" glyph-name="quotesinglbase" horiz-adv-x="381" d="M115 -234V-223Q127 -214 143 -180T172 -100T185 -10Q185 1 179 10T157 34Q139 51 129 65T119 100Q119 126 133 141T172 156Q198 156 221 137T257 85T271 9Q271 -52 250 -109T198
--208T143 -261L115 -234Z" />
-<glyph unicode="&#x201c;" glyph-name="quotedblleft" horiz-adv-x="644" d="M183 430T160 453T124 514T110 595Q110 656 131 708T182 797T237 847H238L265 820V809Q241 790 219 747T196 642Q196 608 206 588T235 542Q249 525 255 514T262 485Q262 459 247 445T208
-430Q183 430 160 453ZM445 430T422 453T386 514T372 595Q372 656 393 708T444 797T499 847H500L528 820V809Q504 790 481 747T458 642Q458 608 468 587T498 542Q512 525 518 514T525 485Q525 459 510 445T471 430Q445 430 422 453Z" />
-<glyph unicode="&#x201d;" glyph-name="quotedblright" horiz-adv-x="644" d="M115 456V467Q128 477 144 503T173 568T185 650Q185 677 176 694T148 732Q133 749 126 761T119 791Q119 817 133 831T172 846Q198 846 221 823T257 762T271 681Q271 620 250 568T199
-479T144 429H143L115 456ZM378 456V467Q391 477 407 503T435 568T447 650Q447 677 438 694T410 732Q395 749 388 761T381 791Q381 817 395 831T434 846Q460 846 483 823T519 762T533 681Q533 620 512 568T461 479T406 429H405L378 456Z" />
-<glyph unicode="&#x201e;" glyph-name="quotedblbase" horiz-adv-x="644" d="M115 -224V-213Q139 -194 162 -151T185 -46Q185 -12 175 8T146 54Q132 71 126 82T119 111Q119 137 133 151T172 166Q198 166 221 143T257 82T271 1Q271 -60 250 -112T199 -201T144 -251H143L115
--224ZM378 -224V-213Q402 -194 424 -151T447 -46Q447 -12 437 8T408 54Q394 71 388 82T381 111Q381 137 395 151T434 166Q460 166 483 143T519 82T533 1Q533 -60 512 -112T461 -201T406 -251H405L378 -224Z" />
-<glyph unicode="&#x2022;" glyph-name="bullet" horiz-adv-x="415" d="M165 238T139 267T112 337Q112 379 142 407T212 435Q251 435 277 408T303 337Q303 296 273 267T203 238Q165 238 139 267Z" />
-<glyph unicode="&#x2039;" glyph-name="guilsinglleft" horiz-adv-x="404" d="M338 520L167 299L338 86L288 52L56 264V333L288 551L338 520Z" />
-<glyph unicode="&#x203a;" glyph-name="guilsinglright" horiz-adv-x="404" d="M348 333V264L116 52L66 86L237 299L66 520L116 551L348 333Z" />
-</font>
-</defs>
-</svg>
diff --git a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.ttf b/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.ttf
deleted file mode 100644
index 4e8f4157b..000000000
Binary files a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.ttf and /dev/null differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.woff b/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.woff
deleted file mode 100644
index 2f2ab4217..000000000
Binary files a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.woff and /dev/null differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.woff2 b/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.woff2
deleted file mode 100644
index 099840930..000000000
Binary files a/themes/xmpp.org/static/fonts/merriweather-v22-latin-regular.woff2 and /dev/null differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v30-latin-300.woff2 b/themes/xmpp.org/static/fonts/merriweather-v30-latin-300.woff2
new file mode 100644
index 000000000..a11988387
Binary files /dev/null and b/themes/xmpp.org/static/fonts/merriweather-v30-latin-300.woff2 differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v30-latin-700.woff2 b/themes/xmpp.org/static/fonts/merriweather-v30-latin-700.woff2
new file mode 100644
index 000000000..a6919a9da
Binary files /dev/null and b/themes/xmpp.org/static/fonts/merriweather-v30-latin-700.woff2 differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v30-latin-900.woff2 b/themes/xmpp.org/static/fonts/merriweather-v30-latin-900.woff2
new file mode 100644
index 000000000..4e3aec929
Binary files /dev/null and b/themes/xmpp.org/static/fonts/merriweather-v30-latin-900.woff2 differ
diff --git a/themes/xmpp.org/static/fonts/merriweather-v30-latin-regular.woff2 b/themes/xmpp.org/static/fonts/merriweather-v30-latin-regular.woff2
new file mode 100644
index 000000000..6515c26fd
Binary files /dev/null and b/themes/xmpp.org/static/fonts/merriweather-v30-latin-regular.woff2 differ


Reviews:
user: login: mwild1
body: :+1: Some small suggestions inline. I have **not** reviewed the layout/presentation aspect.
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-02-28T12:33:37Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-02T17:35:18Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-03T22:27:45Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-03T22:50:55Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-03T22:59:50Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-03T23:20:53Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T09:39:42Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T09:41:14Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T10:15:41Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T10:19:25Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T10:25:15Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T10:25:34Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T10:41:11Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T10:49:28Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T11:08:36Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T11:10:09Z
user: login: ralphm
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T11:32:20Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T13:10:54Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T13:13:46Z
user: login: dwd
body: I've tried taking the edge of some of the more antagonistic comments in the technical briefing, but it's tricky when they're all basically true.  I've also added some suggestions around noting XMPP is a suitable interop choice when considering groupchat and calls; there's probably more we could do here and I think it makes the argument more compelling.
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T13:31:38Z
user: login: guusdk
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T13:49:55Z
user: login: mwild1
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T14:20:34Z
user: login: guusdk
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T14:41:22Z
user: login: dwd
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T14:52:39Z
user: login: dwd
body: Ship it.
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-25T15:33:38Z

Review comments:
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission introduced the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
+
+In this spirit—enabling a truly **competitive market** where users can select messaging providers that align with their **budget, business model, and privacy preferences**—we must return to the **core principle of interoperability: the adoption of open communication standards**.
+
+This is the intent behind the DMA’s requirements.
+
+## Why the XSF is Concerned About Meta’s Proposal and Why XMPP is the Solution
+
+Now that Meta has submitted its proposal for messaging interoperability to the European Commission, we have serious concerns that their approach could not only **preserve the status quo** but also **give Meta even more control over user data**.
+
+### Key Concerns with Meta’s Interoperability Proposal
+
+#### 1. Restrictive Access Through NDAs and Agreements
+
+Meta requires companies to **sign a non-disclosure agreement (NDA)** to access their interoperability detailed documents and likely demands an agreement before enabling interoperability between networks. This effectively **keeps companies in a gatekeeper relationship**, just as Meta did when launching *Messenger for Businesses* to control interactions and ensure benefits flowed primarily to them. 
+
+For competitors, **signing an agreement with Meta grants them disproportionate leverage** due to their massive user base. This is **not true interoperability**—it is a **negotiated privilege**, reinforcing Meta’s dominant position.
+
+Requiring an NDA **prevents non-profit organizations like the XSF** from evaluating or contributing to the interoperability mechanism. It **blocks open-source developers from implementing interoperability** in their software, severely limiting innovation.
+
+#### 2. API-Based Approach Instead of Open Protocols
+
+Meta’s proposal appears to be based on **APIs rather than open protocols**. This is a fundamental problem because:
+
+- **Protocols** are designed for **interop and cooperation**, ensuring long-term stability.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: mwild1
body: ```suggestion
- **Protocols** are designed for **interoperability and cooperation**, ensuring long-term stability.
```
created_at: 2025-02-28T12:23:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission introduced the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: mwild1
body: Slightly tweaked the wording - the DMA is not *only* about messaging.

```suggestion
To prevent extreme concentration of power in the messaging sector, the **European Commission included it firmly within the scope of the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
```
created_at: 2025-02-28T12:26:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission introduced the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
+
+In this spirit—enabling a truly **competitive market** where users can select messaging providers that align with their **budget, business model, and privacy preferences**—we must return to the **core principle of interoperability: the adoption of open communication standards**.
+
+This is the intent behind the DMA’s requirements.
+
+## Why the XSF is Concerned About Meta’s Proposal and Why XMPP is the Solution
+
+Now that Meta has submitted its proposal for messaging interoperability to the European Commission, we have serious concerns that their approach could not only **preserve the status quo** but also **give Meta even more control over user data**.
+
+### Key Concerns with Meta’s Interoperability Proposal
+
+#### 1. Restrictive Access Through NDAs and Agreements
+
+Meta requires companies to **sign a non-disclosure agreement (NDA)** to access their interoperability detailed documents and likely demands an agreement before enabling interoperability between networks. This effectively **keeps companies in a gatekeeper relationship**, just as Meta did when launching *Messenger for Businesses* to control interactions and ensure benefits flowed primarily to them. 
+
+For competitors, **signing an agreement with Meta grants them disproportionate leverage** due to their massive user base. This is **not true interoperability**—it is a **negotiated privilege**, reinforcing Meta’s dominant position.
+
+Requiring an NDA **prevents non-profit organizations like the XSF** from evaluating or contributing to the interoperability mechanism. It **blocks open-source developers from implementing interoperability** in their software, severely limiting innovation.
+
+#### 2. API-Based Approach Instead of Open Protocols
+
+Meta’s proposal appears to be based on **APIs rather than open protocols**. This is a fundamental problem because:
+
+- **Protocols** are designed for **interop and cooperation**, ensuring long-term stability.
+- **APIs** are controlled by the provider and offer a **limited set of features**, with associated **rate limits, fees, and restrictions** that can change over time.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: mwild1
body: Rate limits are a fundamental abuse prevention technique at all levels of the stack. Proposing "usage limits" for clarity in the context of APIs.

```suggestion
- **APIs** are controlled by the provider and offer a **limited set of features**, with associated **usage limits, fees, and restrictions** that can change over time.
```
created_at: 2025-02-28T12:27:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission introduced the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
+
+In this spirit—enabling a truly **competitive market** where users can select messaging providers that align with their **budget, business model, and privacy preferences**—we must return to the **core principle of interoperability: the adoption of open communication standards**.
+
+This is the intent behind the DMA’s requirements.
+
+## Why the XSF is Concerned About Meta’s Proposal and Why XMPP is the Solution
+
+Now that Meta has submitted its proposal for messaging interoperability to the European Commission, we have serious concerns that their approach could not only **preserve the status quo** but also **give Meta even more control over user data**.
+
+### Key Concerns with Meta’s Interoperability Proposal
+
+#### 1. Restrictive Access Through NDAs and Agreements
+
+Meta requires companies to **sign a non-disclosure agreement (NDA)** to access their interoperability detailed documents and likely demands an agreement before enabling interoperability between networks. This effectively **keeps companies in a gatekeeper relationship**, just as Meta did when launching *Messenger for Businesses* to control interactions and ensure benefits flowed primarily to them. 
+
+For competitors, **signing an agreement with Meta grants them disproportionate leverage** due to their massive user base. This is **not true interoperability**—it is a **negotiated privilege**, reinforcing Meta’s dominant position.
+
+Requiring an NDA **prevents non-profit organizations like the XSF** from evaluating or contributing to the interoperability mechanism. It **blocks open-source developers from implementing interoperability** in their software, severely limiting innovation.
+
+#### 2. API-Based Approach Instead of Open Protocols
+
+Meta’s proposal appears to be based on **APIs rather than open protocols**. This is a fundamental problem because:
+
+- **Protocols** are designed for **interop and cooperation**, ensuring long-term stability.
+- **APIs** are controlled by the provider and offer a **limited set of features**, with associated **rate limits, fees, and restrictions** that can change over time.
+
+The industry has already seen the dangers of relying on APIs—as seen with Twitter, Facebook, and Reddit, where API access was restricted or monetized, disrupting their entire ecosystems. **No sustainable business or long-term project can be built on API access alone.**
+
+#### 3. Client-Side Approach Risks User Tracking
+
+Meta’s approach appears to **force external users to behave as if they are Meta users**, meaning:
+
+- Their **identifiers** would exist within Meta’s system.
+- Through the metadata flowing to their platform, **Meta could track external users**, even if they are not Meta users.
+- If **phone numbers are required as identifiers**, it would enable **cross-platform tracking** and **user matching**, further consolidating Meta’s data collection practices.
+
+This raises serious privacy concerns, particularly for users who explicitly **do not want to be part of Meta’s ecosystem**.
+
+#### 4. The Scalability Problem: API Bridges Do Not Work
+
+Relying on APIs for interoperability is inefficient and **does not scale**. Consider this scenario:
+
+- If a messaging service wants to interoperate with 10 providers, it must **develop and maintain 10 separate API bridges**.
+- This approach is **not sustainable**, as the cost and maintenance overhead would deter smaller players from participating.
+- Worse, **platforms could exploit this loophole to avoid true interoperability**. For example, if Meta and Telegram each offer APIs but neither is willing to implement the other's API, they can both claim they are open to interoperability—while **ensuring that nothing actually happens**. This **completely undermines the intent of the DMA**.
+
+### Understanding federation: A Telephone Analogy: Why Meta’s Approach is Flawed**
+
+This is why the **XMPP Standards Foundation (XSF) steps in** and propose to enable interoperability on federation principles which are at the hearth of the Internet majors protocols and allowed it to stay open.
+
+To better understand the shortcomings of Meta’s proposal, we can compare it to another essential communication system: **the global phone network**.
+
+Today, phone networks are **interoperable and federated**. No matter which provider you use, you can call anyone on another network—whether it's a landline or mobile service. **You do not need an account with every provider to communicate.** This seamless federation is possible because:
+
+1. **A standardized common protocol** ensures universal communication.
+2. **A distributed ID attribution system** allows calls to be routed correctly between providers.
+
+The **same model can and should be applied to messaging interoperability**. 
+
+The XMPP Standards Foundation has already done the heavy lifting: by **adopting the XMPP S2S protocol as the interoperability standard**, we can **achieve the same seamless communication in messaging**.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: mwild1
body: This is a technical document, but this abbreviation may not be familiar to readers outside the community.

```suggestion
The XMPP Standards Foundation has already done the heavy lifting: by **adopting the XMPP S2S (server-to-server) protocol as the interoperability standard**, we can **achieve the same seamless communication in messaging**.
```
created_at: 2025-02-28T12:29:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: These look like hyphens, not emdashes? Maybe it's the font.
created_at: 2025-03-02T16:37:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: All these (except the last) are problems to consumers and competitors, rather than problems for Meta. There are problems to Meta as well, for example they have to maintain these APIs for third parties, manage the legal aspects of the NDAs, handle the compliance issues of tracking third-party users as well as third-parties tracking their own users, etc.

Can we rephrase to highlight the costs to Meta?
created_at: 2025-03-02T16:41:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
+
+## Meta Has Already Used XMPP—Why Not Now?
+
+Meta has previously **supported XMPP in Facebook Messenger** and **WhatsApp was built on an XMPP-based server**. The protocol is already battle-tested at scale. Furthermore, **Meta is embracing federation for Threads with ActivityPub**, proving that interoperability works when it serves Meta’s strategic interests.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: Reverse the clauses in the first sentence, I think it's more effective. So "WhatsApp was built on XMPP, and Meta has previously supported XMPP in Facebook Messenger".
created_at: 2025-03-02T16:44:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
+
+## Meta Has Already Used XMPP—Why Not Now?
+
+Meta has previously **supported XMPP in Facebook Messenger** and **WhatsApp was built on an XMPP-based server**. The protocol is already battle-tested at scale. Furthermore, **Meta is embracing federation for Threads with ActivityPub**, proving that interoperability works when it serves Meta’s strategic interests.
+
+If Threads can federate, so can Messenger and WhatsApp.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: Again, flip for symmetry.
created_at: 2025-03-02T16:44:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
+
+## Meta Has Already Used XMPP—Why Not Now?
+
+Meta has previously **supported XMPP in Facebook Messenger** and **WhatsApp was built on an XMPP-based server**. The protocol is already battle-tested at scale. Furthermore, **Meta is embracing federation for Threads with ActivityPub**, proving that interoperability works when it serves Meta’s strategic interests.
+
+If Threads can federate, so can Messenger and WhatsApp.
+
+## A Call to Action
+
+We urge Meta to **adopt XMPP for messaging interoperability**. The **XMPP Standards Foundation (XSF)** is ready to collaborate, evolve the protocol to meet modern needs, and ensure true compliance with the DMA. Let’s build an open, competitive messaging ecosystem—one that empowers users, not just gatekeepers.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: Again, what's in it for Meta, when they are the gatekeeper?

Let's build an open, competitive messaging ecosystem - one that benefits both users and service providers.
created_at: 2025-03-02T16:46:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: I'd change these to be "catchphrase: detail", so "**Seamless Federation**: Connecting users across providers, just like email or phone networks" and so on. I think it'll stand out better on the page, and mirror what's in the previous section better.
created_at: 2025-03-02T16:49:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: Do we need to stress that the XSF, and XMPP as a whole, is independent of any vendor?
created_at: 2025-03-02T16:52:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: I think you want to mention here that WhatsApp started as an XMPP service with a locked-in client. (Although it is mentioned later).
created_at: 2025-03-02T17:00:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission included it firmly within the scope of the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
+
+In this spirit—enabling a truly **competitive market** where users can select messaging providers that align with their **budget, business model, and privacy preferences**—we must return to the **core principle of interoperability: the adoption of open communication standards**.
+
+This is the intent behind the DMA’s requirements.
+
+## Why the XSF is Concerned About Meta’s Proposal and Why XMPP is the Solution
+
+Now that Meta has submitted its proposal for messaging interoperability to the European Commission, we have serious concerns that their approach could not only **preserve the status quo** but also **give Meta even more control over user data**.
+
+### Key Concerns with Meta’s Interoperability Proposal
+
+#### 1. Restrictive Access Through NDAs and Agreements
+
+Meta requires companies to **sign a non-disclosure agreement (NDA)** to access their interoperability detailed documents and likely demands an agreement before enabling interoperability between networks. This effectively **keeps companies in a gatekeeper relationship**, just as Meta did when launching *Messenger for Businesses* to control interactions and ensure benefits flowed primarily to them. 
+
+For competitors, **signing an agreement with Meta grants them disproportionate leverage** due to their massive user base. This is **not true interoperability**—it is a **negotiated privilege**, reinforcing Meta’s dominant position.
+
+Requiring an NDA **prevents non-profit organizations like the XSF** from evaluating or contributing to the interoperability mechanism. It **blocks open-source developers from implementing interoperability** in their software, severely limiting innovation.
+
+#### 2. API-Based Approach Instead of Open Protocols
+
+Meta’s proposal appears to be based on **APIs rather than open protocols**. This is a fundamental problem because:
+
+- **Protocols** are designed for **interoperability and cooperation**, ensuring long-term stability.
+- **APIs** are controlled by the provider and offer a **limited set of features**, with associated **usage limits, fees, and restrictions** that can change over time.
+
+The industry has already seen the dangers of relying on APIs—as seen with Twitter, Facebook, and Reddit, where API access was restricted or monetized, disrupting their entire ecosystems. **No sustainable business or long-term project can be built on API access alone.**
+
+#### 3. Client-Side Approach Risks User Tracking
+
+Meta’s approach appears to **force external users to behave as if they are Meta users**, meaning:
+
+- Their **identifiers** would exist within Meta’s system.
+- Through the metadata flowing to their platform, **Meta could track external users**, even if they are not Meta users.
+- If **phone numbers are required as identifiers**, it would enable **cross-platform tracking** and **user matching**, further consolidating Meta’s data collection practices.
+
+This raises serious privacy concerns, particularly for users who explicitly **do not want to be part of Meta’s ecosystem**.
+
+#### 4. The Scalability Problem: API Bridges Do Not Work
+
+Relying on APIs for interoperability is inefficient and **does not scale**. Consider this scenario:
+
+- If a messaging service wants to interoperate with 10 providers, it must **develop and maintain 10 separate API bridges**.
+- This approach is **not sustainable**, as the cost and maintenance overhead would deter smaller players from participating.
+- Worse, **platforms could exploit this loophole to avoid true interoperability**. For example, if Meta and Telegram each offer APIs but neither is willing to implement the other's API, they can both claim they are open to interoperability—while **ensuring that nothing actually happens**. This **completely undermines the intent of the DMA**.
+
+### Understanding federation: A Telephone Analogy: Why Meta’s Approach is Flawed
+
+This is why the **XMPP Standards Foundation (XSF) steps in** and propose to enable interoperability on federation principles which are at the hearth of the Internet majors protocols and allowed it to stay open.
+
+To better understand the shortcomings of Meta’s proposal, we can compare it to another essential communication system: **the global phone network**.
+
+Today, phone networks are **interoperable and federated**. No matter which provider you use, you can call anyone on another network—whether it's a landline or mobile service. **You do not need an account with every provider to communicate.** This seamless federation is possible because:
+
+1. **A standardized common protocol** ensures universal communication.
+2. **A distributed ID attribution system** allows calls to be routed correctly between providers.
+
+The **same model can and should be applied to messaging interoperability**. 
+
+The XMPP Standards Foundation has already done the heavy lifting: by **adopting the XMPP S2S (server-to-server) protocol as the interoperability standard**, we can **achieve the same seamless communication in messaging**.
+
+## Interoperability Through XMPP Federation
+
+The most effective approach to achieving interoperability is **federation**. This is the principle that underpins **email** and **decentralized federated social networks**, such as those using **ActivityPub (e.g., Mastodon)** or custom approaches like **Bluesky**.
+
+Meta argues against **messaging federation**, claiming that they need to **protect their users from spam, abuse, and security threats**. While user protection is important, this **does not mean federation is inherently unsafe**. In fact, **XMPP was designed with these concerns in mind**—its goal is to support a **sustainable, global-scale federated messaging network** with **built-in security, moderation, and control mechanisms**.
+
+### How Federation Works
+
+In a federated system, a user identifier consists of **two components**:
+
+1. **The domain name** – This serves as the **first level of routing** for messages and interactions, much like an email address (e.g., `user@domain123.eu`). It ensures that messages are **delivered to the correct provider**.
+2. **The username, identifier, or key** – This is assigned by the domain’s provider and **routes communication internally** to the specific user. Importantly, **it does not need to expose private information** and can be processed internally to **protect user privacy**.
+
+Federation enables **server-to-server (s2s) communication**, providing a **flexible and privacy-focused** solution for interoperability. With email, knowing a public address (e.g., `user@domain123.eu`) allows communication **without exposing sensitive details** like the user phone number. The same principle applies to federated protocols like **XMPP and ActivityPub**.
+
+### How Federation Enhances Security & Control
+
+A common misconception is that **federation compromises security**. In reality, **federation offers strong safeguards** while still allowing **providers to enforce moderation and control**. 
+
+Federated systems use a **clear separation between internal and external communication**:
+
+1. **Client-to-Server (c2s) Protocol** – Manages communication between **a provider and its internal users**. Users authenticate through this endpoint with their credentials.
+2. **Server-to-Server (s2s) Protocol** – Handles **external communication between providers**, ensuring that **internal user traffic remains isolated** from external threats.
+
+This gives all providers, including Meta, the opportunity to put **multiple layers of protection** in place:
+
+1. **Separation of internal and external traffic**  
+   - Internal user traffic and external communication are processed **on separate endpoints**.
+   - In emergencies, providers can **completely block external traffic** while **keeping internal messaging functional**.
+
+2. **Domain-level moderation and blocking**  
+   - Providers can **ban external domains** that engage in spam, harmful content, or lack proper moderation.  
+
+3. **Improved monitoring and security enforcement**  
+   - Providers can **thoroughly monitor s2s traffic** to **combat spam, DoS attacks, and other security threats**.
+   - Unlike centralized systems, **federation empowers providers to implement their own security policies** without relying on a single entity.
+
+## Meta, Federation, and XMPP
+
+There is no **technical limitation** preventing Meta from supporting **XMPP**—in fact, **Meta has already done so in the past**.
+
+### Meta’s History with XMPP: Proof of Feasibility
+
+Meta (formerly Facebook) has previously supported XMPP in its messaging products:
+
+- **Facebook Messenger** originally supported XMPP but later discontinued compliance. This shift was **not due to technical constraints**, but rather a **strategic decision** to push users into Meta’s proprietary ecosystem, leveraging its massive user base to create a **network effect** in its favor.
+- **WhatsApp** was originally built using an **open-source XMPP server**—which still **forms the core of its infrastructure** today. 
+  - The **protocol used by WhatsApp** is a **direct derivative of XMPP**, where the XML-based tag system was converted into a **binary format** for **compactness**.  
+  - Despite this change, the **fundamental design and semantics remain identical to XMPP**.
+
+### Meta’s Selective Adoption of Federation
+
+Meta has demonstrated a **willingness to adopt federation**—but **only when it suits its strategic interests**.  
+
+For example, **Threads**, Meta’s social media platform, has committed to **supporting ActivityPub and the Fediverse protocol**. The **Fediverse federation and ID system** function in **the same way that XMPP enables messaging federation**.  
+This **raises an important question**:
+If **Meta is willing to embrace federation** for Threads when facing **competition from Twitter/X and Bluesky**, why is it **reluctant to adopt XMPP for messaging interoperability** under the **Digital Markets Act (DMA)?**
+
+The fundamental difference here is not technical. It is strategic:
+
+- In **messaging**, Meta enjoys **market dominance**, with billions of users across **WhatsApp, Messenger, and Instagram**.  
+- In contrast, **Threads is struggling against Twitter/X and Bluesky**—so Meta is embracing federation as a way to level the playing field and gain market share.  
+
+In other words, **Meta embraces open protocols when it benefits from them, but resists them when they threaten its market control**.  
+
+If Meta were genuinely committed to **interoperability**, it would recognize **XMPP as the most viable and proven protocol for federated messaging**—just as it has in the past.
+
+## Building the Future of Messaging
+
+Federation **is not a security risk—it is a scalable, privacy-friendly model** that has already been **proven in global communication networks** like **email and federated social media**. By leveraging the **XMPP server-to-server (s2s) protocol**, messaging services can **achieve true interoperability** while maintaining **security, user privacy, and control**.
+
+### A Call to Meta: Build Your Interoperability Stack on XMPP
+
+We at the XMPP Standards Foundation (XSF) urge Meta to build its interoperability framework on top of XMPP federation.  
+
+If Threads can implement the Fediverse protocol, there is no reason why Meta cannot do the same with XMPP for Facebook Messenger and WhatsApp—especially since WhatsApp itself was originally built on XMPP.
+
+### The XSF Welcomes Collaboration
+
+The XSF is an open and inclusive organization, welcoming contributions from companies, developers, vendors, and network operators. We recognize that, while Messenger and WhatsApp were originally based on XMPP, there may still be technical discussions needed to align the protocol with Meta’s current needs.
+
+If Meta has specific requirements, such as:
+
+- Features unique to Facebook Messenger or WhatsApp
+- Scalability considerations due to the size of Meta’s user base  
+- New extensions to address Meta’s specific use cases  
+
+The XSF is the right place to have these discussions. Our mission is to evolve and improve federated messaging standards.
+
+### Join the Conversation on the Future of Federated Messaging
+
+We understand that Meta may wish to contribute to the development of XMPP, and we would welcome Meta’s most prominent messaging experts to bring their expertise, concerns, and ideas into the work of the XMPP Standards Foundation.
+
+Let’s work together to build a truly interoperable, open, and competitive messaging future.
+
+***
+
+### Contact Information
+
+Press and general inquiries: [info@xmpp.org](mailto:info@xmpp.org)
+
+Ralph Meijer  
+[Chair of the Board](/about/xsf/people#chair)  
+XMPP: [ralphm@ik.nu](xmpp:ralphm@ik.nu)  
+Mail: [ralphm@ik.nu](mailto:ralphm@ik.nu)
+
+Matthew Wild  
+[Executive Director](/about/xsf/people#executive-director)  
+XMPP: [me@matthewwild.co.uk](xmpp:me@matthewwild.co.uk)  
+Mail: [me@matthewwild.co.uk](mailto:me@matthewwild.co.uk)
+
+Mickaël Rémond  
+Member and Author  
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: We should give Mickael a special title. Liaison or something.
created_at: 2025-03-02T17:08:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: This briefing is very much aimed at an audience of the EU and press, rather than Meta, which it's frankly quite brutal about (though not incorrect). Would this be included in the letter as sent to meta?
created_at: 2025-03-02T17:10:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
path: content/about/open-letter-meta-dma/_index.md
user: login: ralphm
body: They are nice and long in the Merriweather Serif font, see also @guusdk's screenshot.
created_at: 2025-03-03T22:27:45Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
path: content/about/open-letter-meta-dma/_index.md
user: login: ralphm
body: The reason that Meta is working on interoperability here is primarily because of the DMA, so it is not surprising that the issues for competitors are highlighted.

I could amend as follows, additions in italic. 

> - **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, ~and~ do not scale for true federation, _and have to maintained_.
>
> - **User Tracking Risks:** The approach ~risks exposing external users to Meta’s data collection practices~ _involves compliance issues of tracking third-party users at Meta, as well as third-parties tracking Meta's users_.
>
> - **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient, prevents sustainable competition.

created_at: 2025-03-03T22:50:55Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
path: content/about/open-letter-meta-dma/_index.md
user: login: ralphm
body: This also aligns with @guusdk's comment.
created_at: 2025-03-03T22:59:50Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: ralphm
body: I would add in the next paragraph (in italic):

> For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. _The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor._ [..]
created_at: 2025-03-03T23:20:53Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: I think that is a great change.
created_at: 2025-03-04T09:39:41Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: That's perfect.
created_at: 2025-03-04T09:41:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: ralphm
body: I think we cannot separate them. The letter is too short for substance on its own, so the briefing goes into detail. Meta has the burden/privilege of being a (two-fold) gatekeeper in this area. The letter and briefing have to be seen in light of *why* the EU Commission has designated them as gatekeeper. The EU Commission created this situation by focusing the debate on market competition (hence _Digital Markets Act_), rather than looking to effects on users, and by restricting the current debate to instant messaging only. Advanced (but perceived as must-have by end-users) features like voice and video calling are due in about 2 years.
created_at: 2025-03-04T10:15:41Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: ralphm
body: I added a clause in [cd46751](https://github.com/xsf/xmpp.org/pull/1495/commits/cd46751edf74f61167cbaf2dbf3f523f85db558a).
created_at: 2025-03-04T10:19:25Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: ralphm
body: Added in [3cfa1bb](https://github.com/xsf/xmpp.org/pull/1495/commits/3cfa1bb4f8cddd2c1ae0452840497be6064359de)
created_at: 2025-03-04T10:25:15Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
path: content/about/open-letter-meta-dma/_index.md
user: login: ralphm
body: Added in [53a2c9b](https://github.com/xsf/xmpp.org/pull/1495/commits/53a2c9baa560c0cc36f3c390728ae970febe70b4)
created_at: 2025-03-04T10:25:34Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: Apologies for being picky, but I think these need to match the capitalisation.
created_at: 2025-03-04T10:41:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: Hmmm... OK, I think I can work with this and suggest some edits on the technical briefing that will make it less of a bitter pill to swallow. The voice/video aspects are really interesting, since even if they're not covered by the regulations today they clearly will need to be in the future.
created_at: 2025-03-04T10:49:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: ralphm
body: From the DMA, article 7:

```
2.   The gatekeeper shall make at least the following basic
     functionalities referred to in paragraph 1 interoperable where
     the gatekeeper itself provides those functionalities to its own
     end users:

(a) following the listing in the designation decision pursuant to Article 3(9):
    (i) end-to-end text messaging between two individual end users;
    (ii) sharing of images, voice messages, videos and other attached
    files in end to end communication between two individual end
    users;

(b) within 2 years from the designation:
    (i) end-to-end text messaging within groups of individual end
    users;
   (ii) sharing of images, voice messages, videos and other attached
   files in end-to-end communication between a group chat and an
   individual end user;

(c) within 4 years from the designation:
   (i) end-to-end voice calls between two individual end users;
   (ii) end-to-end video calls between two individual end users;
   (iii) end-to-end voice calls between a group chat and an individual
        end user;
   (iv) end-to-end video calls between a group chat and an individual
        end user.
```

With the designation on September 6 2023, the respective dates are a) March 6 2024, b) September 6 2025, and c) September 2027.
created_at: 2025-03-04T11:08:36Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
path: content/about/open-letter-meta-dma/_index.md
user: login: ralphm
body: In 2265e6ab.
created_at: 2025-03-04T11:10:09Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
+
+WhatsApp took a strategic approach by leveraging a public resource—the phone number system—as a unique user identifier. Combined with easy access to users’ phone contacts in modern smartphone operating systems, WhatsApp was able to build an extensive **proprietary** messaging network. In essence, it **became the new ICQ**, but at an even larger scale. As the service grew, it positioned itself **in direct competition with mobile carriers**, as **over-the-top (OTT) messaging**—services that bypass traditional carrier networks by leveraging the open internet. At the time, **net neutrality** was seen as a safeguard ensuring that carriers could not abuse their control over communication infrastructure, but it also allowed closed proprietary messaging services to thrive.
+
+### The Pivotal Year: 2014 and the Rise of Messaging Gatekeeping
+
+The year **2014** marked a critical turning point—one that was especially significant for Meta (formerly Facebook). That year:
+
+- **Facebook acquired WhatsApp for $19 billion**, despite the company's financial losses, signaling the strategic importance of controlling messaging at scale.
+- **Facebook deprecated XMPP support in Facebook Messenger** and in **2015, completely removed its XMPP-based interoperability tool**.
+
+When Facebook eliminated XMPP support, they simultaneously [announced the Messenger Platform at their F8 conference](https://developers.facebook.com/blog/post/2015/03/25/introducing-messenger-platform-and-businesses-on-messenger/), introducing a new ecosystem where **businesses could engage with users under Facebook’s controlled environment**. The move to deprecate XMPP was not a technical necessity but a strategic decision—by restricting APIs and interoperability, Facebook ensured that businesses had no choice but to operate within its platform, using its own tools, while Facebook retained complete control over user engagement and data monetization.
+
+### The Consequences: A Fully Closed Messaging Landscape
+
+Facebook was not alone in this strategy, but it played an **instrumental role in locking down messaging communication** before full interoperability could be realized. What makes this situation even more frustrating is that:
+
+- **Facebook Messenger originally supported XMPP**.
+- **WhatsApp has always been built on an XMPP-based server**—its **internal logic remains rooted in XMPP**, yet it operates as a completely closed system.
+- Both used the same open source XMPP server to bootstrap their infrastructure.
+
+As a result, we have **regressed to a fragmented messaging landscape reminiscent of 1999**, before the emergence of federated interoperability. Today, **multiple closed messaging ecosystems compete to dominate the communication space**, including:
+
+- **Facebook Messenger**
+- **WhatsApp**
+- **Instagram private messaging**
+- **Telegram**
+- **WeChat**
+- **LinkedIn Messaging**
+- **Various Google messaging services**
+- And many more
+
+Each of these services **operates in isolation**, forcing users to either create accounts on multiple platforms to stay in touch with all their contacts or rely on a single provider—driving further concentration in the sector. If a user chooses to focus on just one app, they must convince all their contacts to do the same, effectively reinforcing a **global-scale monopoly** in communication.
+
+### Beyond Messaging: The Broader Lock-In of Communication
+
+What is worst, is that this issue is no longer limited to text-based messaging. Modern messengers have expanded to **voice and video calls**, effectively **controlling digital communication as a whole**. If we do not change course, the endgame is clear, as we are stuck in a race toward a **global monopoly on internet communication**, where a handful of gatekeepers could dictate their terms, limiting competition and user freedom.
+
+## The European Commission and the Digital Markets Act
+
+To prevent extreme concentration of power in the messaging sector, the **European Commission included it firmly within the scope of the Digital Markets Act (DMA)**. Its goal is to ensure that communication remains **open, fair, and competitive**, preventing a future where global messaging is controlled by a **monopoly, duopoly, or, at best, an oligopoly**. Enforcing interoperability is the only way to allow users to **freely choose their preferred messaging provider** rather than being locked into dominant platforms.
+
+In this spirit—enabling a truly **competitive market** where users can select messaging providers that align with their **budget, business model, and privacy preferences**—we must return to the **core principle of interoperability: the adoption of open communication standards**.
+
+This is the intent behind the DMA’s requirements.
+
+## Why the XSF is Concerned About Meta’s Proposal and Why XMPP is the Solution
+
+Now that Meta has submitted its proposal for messaging interoperability to the European Commission, we have serious concerns that their approach could not only **preserve the status quo** but also **give Meta even more control over user data**.
+
+### Key Concerns with Meta’s Interoperability Proposal
+
+#### 1. Restrictive Access Through NDAs and Agreements
+
+Meta requires companies to **sign a non-disclosure agreement (NDA)** to access their interoperability detailed documents and likely demands an agreement before enabling interoperability between networks. This effectively **keeps companies in a gatekeeper relationship**, just as Meta did when launching *Messenger for Businesses* to control interactions and ensure benefits flowed primarily to them. 
+
+For competitors, **signing an agreement with Meta grants them disproportionate leverage** due to their massive user base. This is **not true interoperability**—it is a **negotiated privilege**, reinforcing Meta’s dominant position.
+
+Requiring an NDA **prevents non-profit organizations like the XSF** from evaluating or contributing to the interoperability mechanism. It **blocks open-source developers from implementing interoperability** in their software, severely limiting innovation.
+
+#### 2. API-Based Approach Instead of Open Protocols
+
+Meta’s proposal appears to be based on **APIs rather than open protocols**. This is a fundamental problem because:
+
+- **Protocols** are designed for **interoperability and cooperation**, ensuring long-term stability.
+- **APIs** are controlled by the provider and offer a **limited set of features**, with associated **usage limits, fees, and restrictions** that can change over time.
+
+The industry has already seen the dangers of relying on APIs—as seen with Twitter, Facebook, and Reddit, where API access was restricted or monetized, disrupting their entire ecosystems. **No sustainable business or long-term project can be built on API access alone.**
+
+#### 3. Client-Side Approach Risks User Tracking
+
+Meta’s approach appears to **force external users to behave as if they are Meta users**, meaning:
+
+- Their **identifiers** would exist within Meta’s system.
+- Through the metadata flowing to their platform, **Meta could track external users**, even if they are not Meta users.
+- If **phone numbers are required as identifiers**, it would enable **cross-platform tracking** and **user matching**, further consolidating Meta’s data collection practices.
+
+This raises serious privacy concerns, particularly for users who explicitly **do not want to be part of Meta’s ecosystem**.
+
+#### 4. The Scalability Problem: API Bridges Do Not Work
+
+Relying on APIs for interoperability is inefficient and **does not scale**. Consider this scenario:
+
+- If a messaging service wants to interoperate with 10 providers, it must **develop and maintain 10 separate API bridges**.
+- This approach is **not sustainable**, as the cost and maintenance overhead would deter smaller players from participating.
+- Worse, **platforms could exploit this loophole to avoid true interoperability**. For example, if Meta and Telegram each offer APIs but neither is willing to implement the other's API, they can both claim they are open to interoperability—while **ensuring that nothing actually happens**. This **completely undermines the intent of the DMA**.
+
+### Understanding federation: A Telephone Analogy: Why Meta’s Approach is Flawed
+
+This is why the **XMPP Standards Foundation (XSF) steps in** and propose to enable interoperability on federation principles which are at the hearth of the Internet majors protocols and allowed it to stay open.
+
+To better understand the shortcomings of Meta’s proposal, we can compare it to another essential communication system: **the global phone network**.
+
+Today, phone networks are **interoperable and federated**. No matter which provider you use, you can call anyone on another network—whether it's a landline or mobile service. **You do not need an account with every provider to communicate.** This seamless federation is possible because:
+
+1. **A standardized common protocol** ensures universal communication.
+2. **A distributed ID attribution system** allows calls to be routed correctly between providers.
+
+The **same model can and should be applied to messaging interoperability**. 
+
+The XMPP Standards Foundation has already done the heavy lifting: by **adopting the XMPP S2S (server-to-server) protocol as the interoperability standard**, we can **achieve the same seamless communication in messaging**.
+
+## Interoperability Through XMPP Federation
+
+The most effective approach to achieving interoperability is **federation**. This is the principle that underpins **email** and **decentralized federated social networks**, such as those using **ActivityPub (e.g., Mastodon)** or custom approaches like **Bluesky**.
+
+Meta argues against **messaging federation**, claiming that they need to **protect their users from spam, abuse, and security threats**. While user protection is important, this **does not mean federation is inherently unsafe**. In fact, **XMPP was designed with these concerns in mind**—its goal is to support a **sustainable, global-scale federated messaging network** with **built-in security, moderation, and control mechanisms**.
+
+### How Federation Works
+
+In a federated system, a user identifier consists of **two components**:
+
+1. **The domain name** – This serves as the **first level of routing** for messages and interactions, much like an email address (e.g., `user@domain123.eu`). It ensures that messages are **delivered to the correct provider**.
+2. **The username, identifier, or key** – This is assigned by the domain’s provider and **routes communication internally** to the specific user. Importantly, **it does not need to expose private information** and can be processed internally to **protect user privacy**.
+
+Federation enables **server-to-server (s2s) communication**, providing a **flexible and privacy-focused** solution for interoperability. With email, knowing a public address (e.g., `user@domain123.eu`) allows communication **without exposing sensitive details** like the user phone number. The same principle applies to federated protocols like **XMPP and ActivityPub**.
+
+### How Federation Enhances Security & Control
+
+A common misconception is that **federation compromises security**. In reality, **federation offers strong safeguards** while still allowing **providers to enforce moderation and control**. 
+
+Federated systems use a **clear separation between internal and external communication**:
+
+1. **Client-to-Server (c2s) Protocol** – Manages communication between **a provider and its internal users**. Users authenticate through this endpoint with their credentials.
+2. **Server-to-Server (s2s) Protocol** – Handles **external communication between providers**, ensuring that **internal user traffic remains isolated** from external threats.
+
+This gives all providers, including Meta, the opportunity to put **multiple layers of protection** in place:
+
+1. **Separation of internal and external traffic**  
+   - Internal user traffic and external communication are processed **on separate endpoints**.
+   - In emergencies, providers can **completely block external traffic** while **keeping internal messaging functional**.
+
+2. **Domain-level moderation and blocking**  
+   - Providers can **ban external domains** that engage in spam, harmful content, or lack proper moderation.  
+
+3. **Improved monitoring and security enforcement**  
+   - Providers can **thoroughly monitor s2s traffic** to **combat spam, DoS attacks, and other security threats**.
+   - Unlike centralized systems, **federation empowers providers to implement their own security policies** without relying on a single entity.
+
+## Meta, Federation, and XMPP
+
+There is no **technical limitation** preventing Meta from supporting **XMPP**—in fact, **Meta has already done so in the past**.
+
+### Meta’s History with XMPP: Proof of Feasibility
+
+Meta (formerly Facebook) has previously supported XMPP in its messaging products:
+
+- **Facebook Messenger** originally supported XMPP but later discontinued compliance. This shift was **not due to technical constraints**, but rather a **strategic decision** to push users into Meta’s proprietary ecosystem, leveraging its massive user base to create a **network effect** in its favor.
+- **WhatsApp** was originally built using an **open-source XMPP server**—which still **forms the core of its infrastructure** today. 
+  - The **protocol used by WhatsApp** is a **direct derivative of XMPP**, where the XML-based tag system was converted into a **binary format** for **compactness**.  
+  - Despite this change, the **fundamental design and semantics remain identical to XMPP**.
+
+### Meta’s Selective Adoption of Federation
+
+Meta has demonstrated a **willingness to adopt federation**—but **only when it suits its strategic interests**.  
+
+For example, **Threads**, Meta’s social media platform, has committed to **supporting ActivityPub and the Fediverse protocol**. The **Fediverse federation and ID system** function in **the same way that XMPP enables messaging federation**.  
+This **raises an important question**:
+If **Meta is willing to embrace federation** for Threads when facing **competition from Twitter/X and Bluesky**, why is it **reluctant to adopt XMPP for messaging interoperability** under the **Digital Markets Act (DMA)?**
+
+The fundamental difference here is not technical. It is strategic:
+
+- In **messaging**, Meta enjoys **market dominance**, with billions of users across **WhatsApp, Messenger, and Instagram**.  
+- In contrast, **Threads is struggling against Twitter/X and Bluesky**—so Meta is embracing federation as a way to level the playing field and gain market share.  
+
+In other words, **Meta embraces open protocols when it benefits from them, but resists them when they threaten its market control**.  
+
+If Meta were genuinely committed to **interoperability**, it would recognize **XMPP as the most viable and proven protocol for federated messaging**—just as it has in the past.
+
+## Building the Future of Messaging
+
+Federation **is not a security risk—it is a scalable, privacy-friendly model** that has already been **proven in global communication networks** like **email and federated social media**. By leveraging the **XMPP server-to-server (s2s) protocol**, messaging services can **achieve true interoperability** while maintaining **security, user privacy, and control**.
+
+### A Call to Meta: Build Your Interoperability Stack on XMPP
+
+We at the XMPP Standards Foundation (XSF) urge Meta to build its interoperability framework on top of XMPP federation.  
+
+If Threads can implement the Fediverse protocol, there is no reason why Meta cannot do the same with XMPP for Facebook Messenger and WhatsApp—especially since WhatsApp itself was originally built on XMPP.
+
+### The XSF Welcomes Collaboration
+
+The XSF is an open and inclusive organization, welcoming contributions from companies, developers, vendors, and network operators. We recognize that, while Messenger and WhatsApp were originally based on XMPP, there may still be technical discussions needed to align the protocol with Meta’s current needs.
+
+If Meta has specific requirements, such as:
+
+- Features unique to Facebook Messenger or WhatsApp
+- Scalability considerations due to the size of Meta’s user base  
+- New extensions to address Meta’s specific use cases  
+
+The XSF is the right place to have these discussions. Our mission is to evolve and improve federated messaging standards.
+
+### Join the Conversation on the Future of Federated Messaging
+
+We understand that Meta may wish to contribute to the development of XMPP, and we would welcome Meta’s most prominent messaging experts to bring their expertise, concerns, and ideas into the work of the XMPP Standards Foundation.
+
+Let’s work together to build a truly interoperable, open, and competitive messaging future.
+
+***
+
+### Contact Information
+
+Press and general inquiries: [info@xmpp.org](mailto:info@xmpp.org)
+
+Ralph Meijer  
+[Chair of the Board](/about/xsf/people#chair)  
+XMPP: [ralphm@ik.nu](xmpp:ralphm@ik.nu)  
+Mail: [ralphm@ik.nu](mailto:ralphm@ik.nu)
+
+Matthew Wild  
+[Executive Director](/about/xsf/people#executive-director)  
+XMPP: [me@matthewwild.co.uk](xmpp:me@matthewwild.co.uk)  
+Mail: [me@matthewwild.co.uk](mailto:me@matthewwild.co.uk)
+
+Mickaël Rémond  
+Member and Author  
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: ralphm
body: In be6b0a53.
created_at: 2025-03-04T11:32:19Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,52 @@
+---
+title: "Open Letter to Meta: Support True Messaging Interoperability with XMPP"
+layout: single_open_letter_meta_dma
+---
+
+The European Digital Markets Act (DMA) is designed to break down walled gardens and enforce messaging interoperability. As a designated gatekeeper, Meta—controlling WhatsApp and Messenger—must comply. However, its current proposal falls short, risking further entrenchment of its dominance rather than fostering genuine competition.
+
+## The Problem with Meta’s Interoperability Plan
+
+Meta's proposed approach relies on restrictive NDAs, proprietary APIs, and centralized control. This is **not true interoperability**—it is a closed system that forces third parties to operate within Meta’s terms, undermining the spirit of the DMA. Key issues include:
+
+- **Gatekeeper Agreements:** Companies must sign NDAs to access interoperability details, creating artificial barriers.
+
+- **API-Based Control:** APIs limit flexibility, can be modified unilaterally, and do not scale for true federation.
+
+- **User Tracking Risks:** The approach risks exposing external users to Meta’s data collection practices.
+
+- **Scalability Issues:** Maintaining separate API bridges for each provider is inefficient and prevents sustainable competition.
+
+## The Solution: XMPP Federation
+
+Meta does not need to reinvent interoperability. The **eXtensible Messaging and Presence Protocol (XMPP)** is a **proven, open standard** that has powered global federated messaging for 25 years. XMPP enables **direct server-to-server communication**, removing the need for restrictive agreements and ensuring:
+
+- **Seamless federation** across providers, just like email or phone networks.
+
+- **Decentralized control**, where each service provider can enforce its own policies.
+
+- **Enhanced privacy** by avoiding unnecessary data exposure.
+
+- **Scalability and flexibility**, ensuring long-term sustainability.
path: content/about/open-letter-meta-dma/_index.md
user: login: dwd
body: I feel really bad, but capitals after the colon to match the previous list, please? Sorry!
created_at: 2025-03-04T13:10:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
path: content/about/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: OK, so I'd like to include something somewhere along the lines of:

XMPP not only provides a well-deployed and understood plan for the immediate demands of one-to-one messaging, but a long term path that includes both groupchat and voice/video calls. Just as it would make little sense for Meta to demand anything but WebRTC as the basis for voice/video, we feel it makes little sense demanding anything but XMPP.
created_at: 2025-03-04T13:13:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: Whatever their actual motivation, their proposed interoperability solutions appear [...]
created_at: 2025-03-04T13:18:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: [...] falls short of the European Union's objectives, and offers no clear path to the future requirements. Instead of fostering true interoperability, it risks being seen as [...]
created_at: 2025-03-04T13:20:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: [...] interoperability, including supporting groupchat, voice and video calling, and more over fully open federation.
created_at: 2025-03-04T13:21:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: Should Slack get a mention somewhere in this section too?
created_at: 2025-03-04T13:22:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: Didn't imessage start off on XMPP?
created_at: 2025-03-04T13:23:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: guusdk
body: I _think_ I remember @matt-tucker or @gdombiak point out that Jive Software was supporting Apple, back when I visited ... many, many, _many_ moons ago. That might've been imessage, but I'm not sure at all.
created_at: 2025-03-04T13:49:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: mwild1
body: I've never heard of iMessage using XMPP, but it's not impossible, given its ties to Apple's push notification infrastructure which did use XMPP at some point (and still runs on port 5223).

iChat, on the other hand, was Apple's primary chat client for a long time, and was XMPP-based.
created_at: 2025-03-04T14:20:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: guusdk
body: I probably confused the two. I don't think iMessage even existed when I made that visit.
created_at: 2025-03-04T14:41:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,271 @@
+---
+title: "Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability"
+layout: single_open_letter_meta_dma
+---
+
+## Introduction
+
+The European **[Digital Markets Act (DMA)](https://digital-markets-act.ec.europa.eu/about-dma_en)** was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for **Number-Independent Interpersonal Communication Services (NIICS)**—which includes messaging platforms like WhatsApp and Messenger—to provide true interoperability with third-party services. This requirement is essential to breaking down walled gardens, promoting user choice, and fostering a more competitive digital ecosystem.
+
+The **[XMPP Standards Foundation](https://xmpp.org/about/xmpp-standards-foundation/)** has been closely following the implementation of the Digital Markets Act (DMA) in the European Union, with a specific focus on **messaging interoperability**. As an organization dedicated to open messaging standards, we are committed to helping stakeholders navigate the principles and technical realities of interoperable messaging.
+
+For over 25 years, we have developed and refined the **eXtensible Messaging and Presence Protocol (XMPP)**—a robust, extensible, and open standard that has fostered messaging interoperability worldwide. The XSF, through its membership requirements, and XMPP as a whole, by way of the distributed extensibility of the protocol, are independent of any vendor. Some of our members have been involved since XMPP’s inception in 1999, and several have already provided guidance to the European Union, serving as neutral experts to highlight the extensive resources and expertise our Foundation has cultivated.
+
+However, we now feel compelled to raise our voice more strongly. The direction taken by major gatekeepers of proprietary messaging networks raises serious concerns. Their proposed interoperability solutions appear, at best, as half-measures designed to maintain the status quo and, at worst, as deliberate strategies to reinforce their market dominance under the guise of compliance.
+
+Meta, designated as a [gatekeeper under the DMA](https://digital-markets-act.ec.europa.eu/gatekeepers_en), is the only company in the messaging sector subject to these new interoperability requirements, given its control over WhatsApp and Messenger. Yet, Meta’s current DMA proposal falls short of the European Union’s objectives. Instead of fostering true interoperability, it risks further entrenching Meta’s dominance—strengthening its hold on user data and reinforcing network effects that stifle competition.
+
+With this open letter, we call for a course correction—one that ensures genuine competition and user choice in the messaging space, benefiting individuals, businesses, and the broader digital ecosystem.
+
+## The Role of the XMPP Standards Foundation in the Rise of XMPP
+
+As stated on the XSF website:
+
+> The XMPP Standards Foundation (also known as the XSF and formerly the Jabber Software Foundation) is an independent, nonprofit standards development organisation whose primary mission is to define open protocols for presence, instant messaging, and real-time communication and collaboration on top of the IETF’s Extensible Messaging and Presence Protocol (XMPP).
+>
+> The XSF also provides information and infrastructure to the worldwide community of Jabber/XMPP developers, service providers, and end users.
+
+### Origins and Early Development
+
+In 1999, the goal of the original designers of XMPP was to create an open specification that would enable the emergence of a fully interoperable, federated messaging network. These designers took a pragmatic approach, ensuring that the protocol supported a transition period by supporting server-side bridging. This gateway feature enabled users to merge their legacy communication accounts—at the time primarily ICQ, Yahoo! Messenger, and Microsoft Messenger—into XMPP (then still known as Jabber) as a pivot format. The development and the maintaince of the gateways would happen on the server to adapt to quick change of protocol, but also to ensure the client could use multiple accounts in the most efficient way.
+
+This [Jabber initiative was a success](https://xmpp.org/about/history/). Developers from around the world contributed to making messaging interoperability a reality. As a result, multiple compliant servers and clients were developed, many of them as Open Source software, leading to the emergence of a vast federated network spanning thousands of domains.
+
+### Standardization and Industry Adoption
+
+XMPP was submitted to the **Internet Engineering Task Force (IETF)** and officially became a standard in 2004 under the XMPP name with the publication of **RFC 3920 and RFC 3921**.
+
+Several internet service providers across Europe, including **Libertysurf, SAPO, and 1&1**, deployed XMPP-based clients and services. The protocol gained further momentum in 2005 when **Google Talk** adopted XMPP in a federated setup, enabling large-scale messaging interoperability.
+
+In **May 2008**, **Facebook announced the launch of an XMPP interface** for its Chat service, allowing users to connect via **standard desktop XMPP clients**. While Facebook's internal protocol differed, it still provided a [standards-based Jabber/XMPP interface](https://web.archive.org/web/20100318030410/https://developers.facebook.com/news.php?blog=1&story=361). At the time, **Facebook's XMPP chat documentation** was fully available on its developer pages, reinforcing the significance of XMPP in mainstream communication services ([archived documentation](https://web.archive.org/web/20111006161206/https://developers.facebook.com/docs/chat/)).
+
+In **2009**, **Google placed XMPP at the core of its collaborative editing tool, Google Wave**, further demonstrating the protocol’s adaptability beyond instant messaging. Meanwhile, **social networks across the world embraced XMPP**, with notable implementations by **Yandex in Russia** and **StudiVZ in Germany**.
+
+### A Proven Standard for Messaging Interoperability
+
+XMPP has played a crucial role in shaping the modern messaging landscape. Its success demonstrates that **true interoperability is achievable through open, federated protocols**, and that major technology companies—including Google and Facebook—have previously recognized its value. As the DMA now mandates interoperability for messaging services, XMPP remains the most viable and battle-tested solution to meet these requirements.
+
+## Smartphones, WhatsApp, and the Gatekeeping Strategy
+
+Despite XMPP’s success, technical advantages, and suitability for messaging interoperability, its adoption slowed as the messaging landscape evolved. The shift toward proprietary platforms coincided with the rise of smartphones, which led to growing financial stakes in messaging services and increased efforts by dominant players to consolidate control over their networks.
+
+### The Shift to Mobile and the Rise of Proprietary Networks
+
+In **2007**, Apple launched the iPhone, ushering in the smartphone era and the widespread adoption of mobile internet. By **2009**, the introduction of both the App Store and push notification services paved the way for the launch of **WhatsApp**. Messaging, which had previously been limited to SMS on mobile, quickly became a **rich and ubiquitous communication tool**.
path: content/announcements/open-letter-meta-dma/technical-briefing.md
user: login: dwd
body: Oh, yeah, iChat. That'll be the one I was thinking of.
created_at: 2025-03-04T14:52:39Z
author_association: CONTRIBUTOR

PR comments:
user: login: ralphm
created_at: 2025-02-28T11:53:47Z
body: Note to reviewers: the XSF Board has decided to publish an send this Open Letter to Meta, authored by @mremond. It is accompanied by a detailed technical briefing. I added some custom navigation to collect relevant information in one place. As we want to make sure we communicate this in a coordinated effort, please review this on both the layout and (just) linguistic textual errors.

I have not (yet) linked this from anywhere, so probably we need a short blog post to go with it, which I will author, too. Possibly we should have a section for "press releases" or the likes, which this might be grouped under (instead?). 
author_association: MEMBER
user: login: guusdk
created_at: 2025-02-28T13:28:09Z
body: For your reviewing pleasure, this is a screenshot of the rendered page (based on commit 2ad60b0201d3b2cddb6c1f54d938d1692e9dc5c8 ).

Apart from creating a new section called something like 'press releases', as @ralphm suggested, where this letter could be linked from permanently, we should consider linking it temporarily on the home page. For that, I suggest using the banner that we also use to promote upcoming events.

<details><summary>Screenshot of the letter</summary>

![image](https://github.com/user-attachments/assets/38a3e10a-f7c5-4e18-808b-c6b6b7f04ca1)
</details>
author_association: CONTRIBUTOR
user: login: guusdk
created_at: 2025-02-28T13:30:25Z
body: <details><summary>Screenshot of the technical brief</summary>

![image](https://github.com/user-attachments/assets/9613b656-ce5f-410a-acae-25f363a4b2e0)
</details>
author_association: CONTRIBUTOR
user: login: guusdk
created_at: 2025-02-28T13:35:39Z
body: I'm far from a layout expert, but I'd suggest making these changes:

- Adjust font size or wording so that headings fit on one line
- Make headings more distinct. In the screenshot below, the header "Key Concerns ..." and "1. Restrictive Access..." look to similar
- Have more white space between headings and text

![image](https://github.com/user-attachments/assets/56382577-c378-4b23-ab6f-b1691bea148e)

- What are those two `**` in this heading?

![image](https://github.com/user-attachments/assets/0b107111-e506-43e8-b434-a9de0198ece8)

- Use less bold text. Using bold text to emphasize stuff looses its value if significant parts of the text are being emphasized. To me, it's equivalent of someone chatting in all caps.
author_association: CONTRIBUTOR
user: login: guusdk
created_at: 2025-02-28T13:41:24Z
body: And, very subjectively: in this font, the distinction between bold text and non-bold text is not enough of a distinction. It makes for a very uncomfortable read. Can it be made bolder (or possibly use a different representation for emphasis, like italics)?
author_association: CONTRIBUTOR
user: login: guusdk
created_at: 2025-02-28T13:45:11Z
body: On the letter page itself, consistently use comma's in this list (either use them for each item, or for none of them).

![image](https://github.com/user-attachments/assets/37513bf3-4d1b-42ee-8618-046744bd6af9)

Could we include something that resembles an old-fashioned signature here, to give the letter a bit more the feel of being an actual letter?

![image](https://github.com/user-attachments/assets/4ec95669-6a78-4aa9-af2c-c8cc768b586b)

author_association: CONTRIBUTOR
user: login: ralphm
created_at: 2025-02-28T14:47:30Z
body: @guusdk thanks for that feedback. I looked into the styling of headings (margins, size, and weight), but this is a combination of the defaults for bootstrap and some custom overrides. I am hesitant to change any of this, because it would affect the entire site. I did remove superfluous bolding of two titles (including those double stars), and am looking at adding spacing for two consecutive headings.

As for the commas, each of those items is a sentence, and they just seem to make sense for some but not the others, unless we reword the who thing. I was hoping we didn't have to wordsmith this too much.

The signature is an good idea. Not sure if it is needed, but I'll think about how to best do this.
author_association: MEMBER
user: login: guusdk
created_at: 2025-03-04T12:12:34Z
body: <details>
  <summary>Screenshots based on commit be6b0a53b3c523fc08ecb2e058078262e78f2c01</summary>

![image](https://github.com/user-attachments/assets/1c82cd1f-1e5e-4e36-b95a-70af41d23d11)

![image](https://github.com/user-attachments/assets/eac966c5-cc5d-4156-a995-0430f1a9bc78)
</details>
author_association: CONTRIBUTOR
user: login: guusdk
created_at: 2025-03-04T12:43:43Z
body: If we want to facilitate these documents to be a discussion point within external organizations (meta, EU), then it would be good to make sure that it looks good when printed (on physical paper). When discussing things in a meeting, many people will still use such hard-copies.

Currently, the print (based on a preview on my laptop) of this page looks horrible. The side margins are very wide and the font size is so large that every page only contains a little text.

I think this can be improved a lot by using [a print style sheet](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Printing).

I have no practical experience, but I tried hacking in this very minimal set of style directives for printing, which already makes quite a difference.

```css
@media print {
    .container, .container-lg, .container-md, .container-sm, .container-xl, .container-xxl {
        max-width: unset;
    }
    article p {
        font-size: 10pt;
    }
}
```

There are undoubtedly better ways to do this. Perhaps Bootstrap supports this, but even if that proves to be to much trouble: let's at least do the above.
author_association: CONTRIBUTOR
user: login: mremond
created_at: 2025-03-04T12:50:24Z
body: Thanks for all the improvements !
author_association: CONTRIBUTOR
user: login: dwd
created_at: 2025-03-04T13:07:04Z
body: > Thanks for all the improvements !

Thanks for writing it, and spurring us into action!
author_association: CONTRIBUTOR
user: login: ralphm
created_at: 2025-03-04T14:04:16Z
body: @guusdk good point on the print styling. I'll have a stab at this tomorrow.
author_association: MEMBER
user: login: cal0pteryx
created_at: 2025-03-04T18:54:35Z
body: > I think this can be improved a lot by using [a print style sheet](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Printing).
> 
> There are undoubtedly better ways to do this. Perhaps Bootstrap supports this, but even if that proves to be to much trouble: let's at least do the above.

@guusdk there is a project which claims to add style rules for printing in conjunction with Bootstrap 5: https://github.com/coliff/bootstrap-print-css/blob/main/css/bootstrap-print.css
Maybe this can be used for inspiration.

To avoid spreading the focus in this PR, I'd suggest to do that in a separate PR though (I'd be happy to create one using your suggestion and parts of the linked project as a starting point).
author_association: MEMBER
user: login: mremond
created_at: 2025-03-17T17:16:16Z
body: Hi,
Do you know when we can expect to have it pushed to the XSF website ? I think it may be interesting to have it released even if we want to tweak the stylesheet later on.
Please, let me know if I can be of any help.
Thanks !  
author_association: CONTRIBUTOR
user: login: Echolon
created_at: 2025-03-17T17:26:02Z
body: Hi,

I am with Mickaël: Let's push it out!

I would say of we don't hear back by tomorrow night, let's merge it.

Cheers,
Eddie

17 mar 2025 18:16:46 Mickaël Rémond ***@***.***>:

> mremond left a comment (xsf/xmpp.org#1495)
> 
> Hi,
> Do you know when we can expect to have it pushed to the XSF website ? I think it may be interesting to have it released even if we want to tweak the stylesheet later on.
> Please, let me know if I can be of any help.
> Thanks ! 
> 
> -- 
> Reply to this email directly or view it on GitHub:
> https://github.com/xsf/xmpp.org/pull/1495#issuecomment-2730297754
> You are receiving this because your review was requested.
> 
> Message ID: ***@***.***>

author_association: MEMBER
user: login: ralphm
created_at: 2025-03-17T17:41:09Z
body: I had some personal and business distractions, and will pick this up tomorrow. @Echolon please don't merge this yourself. We need to coordinate some stuff before, and I also want a blog post, that I've started writing, to go with it.
author_association: MEMBER
user: login: ralphm
created_at: 2025-03-25T10:21:15Z
body: @dwd @mremond @guusdk I tweaked the (normal) styling a bit, leaving the print styling out of scope. I also added a blog post. Can you please review, so we can get this out?
author_association: MEMBER
user: login: mremond
created_at: 2025-03-25T15:31:17Z
body: I had a look, and it looks very good to me, many thanks for this !
author_association: CONTRIBUTOR
user: login: ralphm
created_at: 2025-03-25T18:10:59Z
body: Thanks!

@Echolon when published, can you use the following as the post to Mastodon, etc., verbatim?

> Today the XMPP Standards Foundation publishes an Open Letter to urge Meta to adopt XMPP for messaging interoperability. It’s time for real interoperability. Let’s make it happen. Blog post: https://xmpp.org/2025/03/open-letter-to-meta-support-true-messaging-interoperability-with-xmpp/. Open Letter: https://xmpp.org/announcements/open-letter-meta-dma/

The only thing left, then, after publishing, is sending a message to Meta. I'll figure that out, out of band. I hope to have an answer on this shortly, and will then press the button.
author_association: MEMBER