Tweets From WordPress  ## Highlights - Since Sept 17th, 2024, when the whole @wpengine thing started, there have been 28,738,111 downloads of WordPress Core (this includes all versions and all languages), 296,991,952 downloads of plugins, and 7,338,623 downloads of themes. But yes, tell us WordPress is in trouble. 😂 ([View Tweet](https://twitter.com/WordPress/status/1852414666238243190)) - The Security Team will of course work with hosts to protect this vulnerability at the network edge. We want every WordPress to be safe. ([View Tweet](https://twitter.com/WordPress/status/1856111635401777171)) - This is not a WordPress vulnerability, though lots of WordPress users who chose to get their theme through Themeforest, CodeCanyon, etc are being hurt. ([View Tweet](https://twitter.com/WordPress/status/1856111634374164801)) - When you see articles about vulnerabilities like this "Critical WPLMS WordPress Theme" with RCE attacks, note that this is not a theme that goes through the .org directory. It's a theme distributed by Themeforest, CodeCanyon, and WPLMS directly. Be wary of non-.org distribution. ([View Tweet](https://twitter.com/WordPress/status/1856111633258701114)) - We may need to pause work on collaboration, Phase 3 of Gutenberg to focus on resolving this issue. ([View Tweet](https://twitter.com/WordPress/status/1868799980846432694)) - Should this checkbox be required to use the .org login form? ([View Tweet](https://twitter.com/WordPress/status/1868799979231584473)) - It's come to our attention that there is some mishegas around the Bromeliaceae plant pineapples. We need to hear the will of the people. Is pineapple on pizza delicious? ([View Tweet](https://twitter.com/WordPress/status/1868799977071542324)) - The WordPress philosophy is to make it easy for people to leave, so they're more likely to stay. Give freedom and choice. ([View Tweet](https://twitter.com/WordPress/status/1876056553134178524)) - As more people become aware of WPE's business practices they will either need to behave better or continue to bleed customers. Over 33,000 sites have left already, which you can track here: https://t.co/N0J7zNitl3 ([View Tweet](https://twitter.com/WordPress/status/1876056551271829671)) - Here's a Reddit thread showing one customer's struggle to cancel: https://t.co/d2CisND5dB ([View Tweet](https://twitter.com/WordPress/status/1876056549715771903)) - One way @wpengine juices its profits at the expense of its customers is by making it hard to export or cancel your plan, like one of those bad gyms. https://t.co/qg5cXCAs01  ([View Tweet](https://twitter.com/WordPress/status/1876056547274686608)) - We welcome @jdevalk and @karimmarucchi to try their ideas around architecture, governance, and more to give folks a chance to try out alternative leadership. ([View Tweet](https://twitter.com/WordPress/status/1877902089982034352)) - We stand ready to serve. 🫡 https://t.co/0s1YlzN9iA ([View Tweet](https://twitter.com/WordPress/status/1881469141233889435)) - While @automattic is under legal attack, they are matching WPE's hours; they'll have to reduce by 53%. Automattic has been by far and away the largest contributor to the project and core. ([View Tweet](https://twitter.com/WordPress/status/1895108549531033777)) - WP Engine's Five for the Future page now lists 20 hours, since the preliminary injunction guaranteeing their access to .org they are actually contributing less. ([View Tweet](https://twitter.com/WordPress/status/1895108547568165111)) - We need to come together, not suffer internecine warfare. Tremendous resources are being spent on lawyers instead of making WordPress and its ecosystem better. This is at a pivotal time, when the landscape is changing rapidly thanks to AI. ([View Tweet](https://twitter.com/WordPress/status/1895108553389810125)) - The longer WP Engine tries to compete in the courtroom instead of the marketplace, the more WordPress suffers. They continue to refuse any attempt to resolve things amicably so we can all get back to work helping users. ([View Tweet](https://twitter.com/WordPress/status/1895108551414255763)) - After a thoughtful discussion with Core committers, WordPress is moving to one major release per year starting in 2025. Regular maintenance and security releases will continue to keep sites stable and secure between major updates. ([View Tweet](https://twitter.com/WordPress/status/1912562662023553196)) - We’re clearing out all previous human blocks to create a more open and collaborative environment. While community and directory guidelines remain, consider any old blocks to be bugs that are on their way out. ([View Tweet](https://twitter.com/WordPress/status/1917693230096826420)) - Looks like the Federated and Independent Repository project is going great. This is clearly going to rock the WordPress world. We don't know how we'll continue without these contributors. Maybe they need some REST. https://t.co/NCF4C4KNGI ([View Tweet](https://twitter.com/WordPress/status/2009915747254829456)) - The parasite continues to eat the host. The cancer is trying to spread. https://t.co/Bv1lQg6jda ([View Tweet](https://x.com/WordPress/status/2032291317871468554)) - It's cute when companies think customers are dumb and they can openwash their way to a good reputation. https://t.co/5oXkPmw0fC ([View Tweet](https://x.com/WordPress/status/2032295665582108987)) - Dear @bgardner, is it a violation of @FTC paid influencer disclosure guidelines to quote complimentary things about @wpengine in @therepositorywp when you sponsor them? Do you have financial relationships with others quoted in the article? https://t.co/LAg96jn4jN ([View Tweet](https://x.com/WordPress/status/2032551515525661056)) - If you suspect an influencer is not properly disclosing their relationship when advocating for a company that they may be sponsored or an affiliate of, please report it to the @FTC using their form: https://t.co/zQSHncqHMT Fines can reach 50k per violation. ([View Tweet](https://x.com/WordPress/status/2032558032660402596)) - @WiseArts @bgardner Do you currently or have you in the past received any compensation or free services from @wpengine, for example as an affiliate or part of their agency program? ([View Tweet](https://x.com/WordPress/status/2032551919751708767)) - Dear @bgardner, is it a violation of @FTC paid influencer disclosure guidelines to quote complimentary things about @wpengine in @therepositorywp when you sponsor them? Do you have financial relationships with others quoted in the article? https://t.co/LAg96jn4jN ([View Tweet](https://x.com/WordPress/status/2032551515525661056)) - If you suspect an influencer is not properly disclosing their relationship when advocating for a company that they may be sponsored or an affiliate of, please report it to the @FTC using their form: https://t.co/zQSHncqHMT Fines can reach 50k per violation. ([View Tweet](https://x.com/WordPress/status/2032558032660402596)) - @WiseArts @bgardner Do you currently or have you in the past received any compensation or free services from @wpengine, for example as an affiliate or part of their agency program? ([View Tweet](https://x.com/WordPress/status/2032551919751708767)) - "WPackagist was acquired by WP Engine, a private-equity backed company," but now we have WP Composer, with 17x faster cold resolves and CDN caching. Open source always wins. https://t.co/ttmoUr2ZLq ([View Tweet](https://x.com/WordPress/status/2033540005419696173)) - If you were worried about @wpengine acquiring WPackagist, there's a great community-supported alternative from @rootswp: https://t.co/uWzPYRQf9a ([View Tweet](https://x.com/WordPress/status/2033786215594660037)) ## New Highlights added 2026-08-21 at 11:52 PM - Ouch, telling people not to update... this wasn't a bug in 7.1. Perhaps consider your usage of @wp_rocket. This is also part of the risk of using plugins outside the official plugin directory, which has many alternatives that seemed fine on the 7.1 release day. https://t.co/IBRmNrstN1 ([View Tweet](https://x.com/WordPress/status/2090983043318390849))