By Devine Lu Linvega

Those are the contents of a post I recently made, but really that and even the replies I made are not the full story Truth is, to get right to the point, the fact that Matrix was accompanied by a for-profit entity, funded by venture capital was the biggest mistake that Matrix as a project has ever made. ## Element is not a friend In roughly the beginning, there was two organizations that came out of the project: The Matrix Foundation and New Vector Ltd / Riot / Element. The _idea_ was for New Vector Ltd to carry out the necessary work and bring in the necessary funding for the Matrix Foundation to thrive. Or well, so I've been told. They had multiple funding rounds lead by the likes of status.im, Automattic, the AI and Web3 company protocol labs and others; You get the gist, lots of VC and similar funding also a questionable amount of “Web3” and ~~bullshit generation~~ AI. Element was then tasked with using that to build the software that would power Matrix. And for a long time, they did that. They relied on the software themselves but kept it in the hands of the Non-Profit Matrix Foundation. Until the 6th of November 2023 when they—in their words—moved to a different repository and to the AGPL license. **In reality, the Foundation did not know this was coming, and a huge support net was pulled away under their feet.** Element's “re-focusing” on “establishing a level playing field” means hostile takeover of all important projects that were under the Matrix Foundation banner and to stop running and managing the Matrix.org homeserver **despite** it still being the default option in Element today. The results of this are, as one may expect, devastating. I don't think I've seen the Matrix Foundation ring the alarm bells any more than today that they need funding to keep the foundation going. Unfortunately, all the money is being swept up by Element instead. Of course I understand there is not really an alternative as of right now; No one else wants to take up Element's job, by which I mean the job that the foundation pays them to do now instead of it being donated to them. Yes, the high expenses for the Matrix.org homeserver are largely because they are still managed by Element, just not as donated work but instead like with any other customer. This also means that the Foundation suffers from Element's decisions and is why they pay a hefty price for what would otherwise not be _this_ expensive. * * * Today this leaves the foundation in a dire situation. So dire in fact that they are starting to adopt things that I can almost guarantee many on the governing board do not like. The Matrix Foundation is making Matrix.org a freemium service. Now, and I can't stress this enough, I really don't think many people at the foundation _want_ this. But with Element sort of just pushing whatever they need in their client and nothing else, I doubt anyone would even be able to get anything implemented in Element to notify Matrix.org users akin to what Thunderbird or KDE started doing in their respective products. As such the governing board does recognize that measures like these are kind of necessary, even if ugly. Either way it shows that Element is seemingly cashing in on selling ,Matrix to governments and B2B as a SaaS solution without it going back to the foundation, without it funding critical parts of the core of matrix that **need** to be revised (like moderation, or a lack thereof) or the Matrix Foundation. * * * At the same time I can't help but think that **this could have been prevented**. Even Matthew himself recognizes that putting the future on Matrix on the line with VC funding and alike was not the best idea for the health of Matrix. Matrix should, from the start, never have been this heavily tied-into and reliant on VC funds to keep the project as a whole afloat. Ultimately, for-profit companies will do what makes them profit, _not_ what's the best option. Unless the best option happens to coincide with making the most profit. Unfortunately, supporting the foundation through anything more than “in spirit” and a platinum membership is out of their budget, apparently. I think that morally they owe a lot more than that. ## So, what now? If you believe Matrix can still thrive despite, in my eyes, being sabotaged by New Vector Ltd, please do go donate. If you're like me, and you've seen Matrix fail too many times and have concerns about the sustainability of some of the core design decisions, there are some other projects you may be interested in. > This list is split into two, things that I personally want to recommend and things that were recommended for me to include by others. Everything I am recommending here specifically _isn't_ tied to VC funds or a for-profit entity, at least not to my knowledge. Personal: * Polyproto / The Polyphony Project – Made by 🏳️‍⚧️ people, aims to have Discord API compatibility and builds a “boring” identity federation protocol with multi-homing and user-owned identity and data in its design. (donate) * Delta chat – Builds on traditional E-Mail standards like SMTP and IMAP, enhancing it with end-to-end-encryption, a custom server stack and a full instant-messenger experience. Additionally has webxdc. (donate) * Revolt? – An open-source discord clone. The `?` is there because whilst it's okay, it is not federated which makes me a bit hesitant to recommend it as an alternative to _matrix_ of all things. other's recommendations: * XMPP/Jabber – battle-tested instant messaging standard with lots of client apps for major platforms. Despite me running an xmpp server I don't personally recommend it due to clients taking a while to catch up with features, i.e how Conversations currently lacks replies and most clients lack the ability to delete/retract messages. * IRCv3 – An evolution of the well-known IRC standard with lots of quality-of-life and functionality improvements that are to be expected from modern chat applications. I haven't personally used it so I can't personally recommend it. Anti-recommendations: * SimpleX Chat – Many suggested this and I will explicitly recommend **_against_** it due to the founder's positions on various topics. This includes being anti-vaxx, believing COVID-19 was a hoax, trans- and homophobia, climate denial; In the SimpleX Groupchat he's also been seen basically bootlicking trump a couple times, but I've lost receipts to that. ## Additions from 09:38 CEST, 16th of June 2025 I saw that this post got shared around in...some room that matthew is in, the details don't really matter to me I wrote this on a relatively short timespan with some public records I found, it's not like I can look into Element's finances **nor that of the foundation** as the financial report is to my knowledge **still** not out despite being “almost finished”. There is some more information shared in that thread now but it is in no way a full breakdown of finances. To answer the question of “where this came from”, I lost my enthusiasm in matrix and this is the result matrix used to be something I was genuinely excited to use on my devices, I talked to _my dad_ about Matrix – which otherwise never hears of these kinds of projects – because I was convinced it was gonna make it, I was convinced Matrix would become the next big IM standard The reality is, after over 10 years...that is not where Matrix ended up. It is less so about fear or doubt and moreso about sadness and disappointment. Call this bait, I just don't feel _excited_ about matrix anymore. * * * # ↓ it'd mean a lot if you supported my work ↓ https://liberapay.com/cyrneko https://ko-fi.com/cyrneko Any little bit helps <3

Local-first code collaboration on a peer-to-peer network

Save and share life’s most important moments—photos, videos, music, PDFs, documents, and more—securely across all your devices.

We did it: Drupal CMS 1.0 is here! 🎉 Eight months ago, I challenged our community to make Drupal easier for marketers, content creators, and site builders. Today, on Drupal's 24th birthday, we're making history with the launch of Drupal CMS 1.0. With this release, you now have two ways to build with Drupal: * **Drupal Core** serves expert users and developers who want complete control over their websites. It provides a blank canvas for building websites and has been the foundation behind millions of websites since Drupal began 24 years ago. * **Drupal CMS** is a ready-to-use platform for marketing teams, content creators and site builders built on Drupal 11 core. When you install Drupal CMS, you get a set of out-of-the-box tools such as advanced media management, SEO tools, AI-driven website building, consent management, analytics, search, automatic updates and more. To celebrate this milestone, more than 60 launch parties are happening around the world today! These celebrations highlight one of Drupal's greatest strengths: a worldwide community that builds and innovates together. If you want to try Drupal CMS, you can start a free trial today at https://www.drupal.org/drupal-cms/trial. ### Built for ambitious marketers Drupal CMS targets organizations with ambitious digital goals, particularly in mid-market and enterprise settings. The platform provides a robust foundation that adapts and scales with evolving needs. Organizations often hit a growth ceiling with non-Drupal CMS platforms. What starts as a simple website becomes a constraint as needs expand. Take privacy and consent management as an example: while these features are now essential due to GDPR, CCPA, and growing privacy concerns, most CMS platforms don't offer them out of the box. This forces organizations to create patchwork solutions. Drupal CMS addresses this by including privacy and consent management tools by default. This not only simplifies setup but also sets a new standard for CMS platforms, promoting a better Open Web – one that prioritizes user privacy while helping organizations meet regulatory requirements. ### Recipes for success The privacy and consent management feature is just one of many 'recipes' available in Drupal CMS. Recipes are pre-configured packages of features, like blogs, events, or case studies, that simplify and speed up site-building. Each recipe automatically installs the necessary modules, sets up content types, and applies configurations, reducing manual setup. This streamlined approach makes Drupal more accessible for beginners but also more efficient for experienced developers. Drupal CMS 1.0 launches with nearly 30 recipes included, many of which are applied by default to provide common functionality that most sites require. Recipes not applied by default are available as optional add-ons and can be applied either during setup or later through the new Project Browser. More recipes are already in development, with plans to release new versions of Drupal CMS throughout the year, each adding fresh recipes. _The Drupal CMS installer lets users choose from predefined 'recipes' like blog, events, case studies and more. Each recipe automatically downloads the required modules, sets up preconfigured content types, and applies the necessary configurations._ ### Pioneering the future, again Drupal CMS not only reduces costs and accelerates time to value with recipes but also stands out with innovative features like AI agents designed specifically for site building. While many platforms use AI primarily for content creation, our AI agents go further by enabling advanced tasks such as creating custom content types, configuring taxonomies, and more. This kind of innovation really connects to Drupal's roots. In its early days, Drupal earned its reputation as a forward-thinking, innovative CMS. We helped pioneer the assembled web (now called 'composable') and contributed to the foundation of Web 2.0, shipping with features like blogging, RSS, and commenting long before the term Web 2.0 existed. Although it happened long ago and many may not remember, Drupal was the first CMS to adopt jQuery. This move played a key role in popularizing jQuery and establishing it as a cornerstone of web development. Curious about what Drupal CMS' AI agents can do? Watch Ivan Zugec's video for a hands-on demonstration of how these tools simplify site-building tasks – even for expert developers. We don't know exactly where AI agents will take us, but I'm excited to explore, learn, and grow. It feels like the early days when we experimented and boldly ventured into the unknown. ### Changing perceptions and reaching more users Drupal has often been seen as complex, but Drupal CMS is designed to change that. Still, we know that simply creating a more user-friendly and easier-to-maintain product isn't enough. After 24 years, many people still hold outdated perceptions shaped by experiences from over a decade ago. Changing those perceptions takes time and deliberate effort. That is why the Drupal CMS initiative is focused not just on building software but also on repositioning and marketing Drupal in a way that highlights how much it has evolved. _The new Drupal.org features a refreshed brand and updated messaging, positioning Drupal as a modern, composable CMS._ To make this happen, we've refreshed our brand and started reworking Drupal.org with the help of the Drupal Association and our Drupal Certified Partners. The updated brand feels fresher, more modern, and more appealing to a larger audience. For the first time, the Drupal Association has hired two full-time product marketers to help communicate our message. Our goal is clear: to help people move past outdated perceptions and see Drupal for what it truly is – a powerful, modern platform for building websites that is becoming more user-friendly, as well as more affordable to use and maintain. ### Achieving bold ambitions through collaboration Launching the Drupal CMS initiative was bold and ambitious, requiring extraordinary effort from our community – and they truly stepped up. It was ambitious because this initiative has been about much more than building a second version of Drupal. It's been a focused and comprehensive effort to expand our market, modernize our brand, accelerate innovation, expand our marketing, and reimagine our partner ecosystem. When I announced Drupal Starshot and Drupal CMS just 8 months ago, I remember turning to the team and asking, "How exactly are we going to pull this off?". We had a lot to figure out – from building a team, setting goals, and mapping a path forward. It was a mix of uncertainty, determination, and maybe a touch of "What have we gotten ourselves into?". A key success factor has been fostering closer collaboration among contributors, agency partners, Drupal Core Committers, Drupal Association staff, and the Drupal Association Board of Directors. This stronger alignment didn't happen by chance; it's the result of thoughtfully structured meetings and governance changes that brought everyone closer together. After just 8 months, the results speak for themselves. Drupal CMS has significantly increased the pace of innovation and the level of contributions to Drupal. It's a testament to what we can achieve when we work together. We've seen a 40% increase in contributor activity since the initiative launch, with over 2,000 commits from more than 300 contributors. _Drupal CMS has been a powerful catalyst for accelerating innovation and collaboration. Since development began in 2024, contributions have soared. Organization credits for strategic initiatives grew by 44% compared to 2023, with individual contributions increasing by 37%. The number of unique contributors rose by 12.5%, and participating organizations grew by 11.3%._ The initiative required me to make a significant time commitment I hadn't anticipated at the start of 2024 – but it's an experience I'm deeply grateful for. The Drupal CMS leadership team met at least twice a week, often more, to tackle challenges head-on. Similarly, I had weekly meetings with the Drupal Association. Along the way we developed new working principles. One key principle was to solve end-user problems first, focusing on what marketers truly need rather than trying to account for every edge case. Another was prioritizing speed over process, enabling us to innovate and adapt quickly. These principles are still evolving, and now that the release is behind us, I'm eager to refine them further with the team. The work we did together was intense, energizing, and occasionally filled with uncertainty about meeting our deadlines. We built strong bonds, learned to make quick, effective decisions, and maintained forward momentum. This experience has left me feeling more connected than ever to our shared mission. ### The Drupal CMS roadmap for 2025 As exciting as this achievement is, some might ask if we've accomplished everything we set out to do. The answer is both yes and no. We've exceeded my expectations in collaboration and innovation, making incredible progress. But there is still much to do. In many ways, we're just getting started. We're less than one-third of the way through our three-year product strategy. With Drupal CMS 1.0 released, 2025 is off to a strong start. Our roadmap for 2025 is clear: we'll launch Experience Builder 1.0, roll out more out-of-the-box recipes for marketers, improve our documentation, roll out our new brand to more parts of Drupal.org, and push forward with innovative experiments. Each step brings us closer to our goal: modernizing Drupal and making Drupal the go-to platform for marketers and developers who want to build ambitious digital experiences — all while championing the Open Web. **Subscribe to my blog** Join 5,000+ subscribers and get new posts by email. Sign up Or subscribe using RSS ### Thank you, Drupal community We built Drupal CMS in a truly open source way – collaboratively, transparently, and driven by community contributions – proving once again that open source is the best way to build software. The success of Drupal CMS 1.0 reflects the work of countless contributors. I'm especially grateful to these key contributors and their organizations (listed alphabetically): Jamie Abrahams (FreelyGive), Gareth Alexander (Zoocha), Martin Anderson-Clutz (Acquia), Tony Barker (Annertech), Pamela Barone (Technocrat), Addison Berry (Drupalize.me), Jim Birch (Kanopi Studios), Baddy Breidert (1xINTERNET), Christoph Breidert (1xINTERNET), Nathaniel Catchpole (Third and Grove / Tag1 Consulting), Cristina Chumillas (Lullabot), Suzanne Dergacheva (Evolving Web), Artem Dmitriiev (1xINTERNET), John Doyle (Digital Polygon), Tim Doyle (Drupal Association), Sascha Eggenberger (Gitlab), Dharizza Espinach (Evolving Web), Tiffany Farriss (Palantir.net), Matthew Grasmick (Acquia), Adam Globus-Hoenich (Acquia), Jürgen Haas (LakeDrops), Mike Herchel (DripYard), J. Hogue (Oomph, Inc), Gábor Hojtsy (Acquia), Emma Horrell (University of Edinburgh), Marcus Johansson (FreelyGive), Nick Koger (Drupal Association), Tim Lehnen (Drupal Association), Pablo López Escobés (Lullabot), Christian López Espínola (Lullabot), Leah Magee (Acquia), Amber Matz (Drupalize.me), Lenny Moskalyk (Drupal Association), Lewis Nyman, Matt Olivera (Lullabot), Shawn Perritt (Acquia), Megh Plunkett (Lullabot), Tim Plunkett (Acquia), Kristen Pol (Salsa Digital), Joe Shindelar (Drupalize.me), Lauri Timmanee (Acquia), Matthew Tift (Lullabot), Laurens Van Damme (Dropsolid), Ryan Witcombe (Drupal Association), Jen Witowski (Lullabot). I also want to recognize our Marketing Committee, the Core Committers, the Drupal Association Board of Directors, and the Drupal Starshot Advisory Council, whose guidance and strategic input shaped this initiative along the way. While I've highlighted some contributors here, I know there are hundreds more who shaped Drupal CMS 1.0 through their code, testing, UX work, feedback, advocacy and more. Each contribution, big or small, moved us forward. To everyone who helped build this milestone: THANK YOU!