TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

WP Engine is banned from WordPress.org

156 点作者 lambda-dev8 个月前

14 条评论

cyral8 个月前
The exaggerations in the post are crazy, that WP engine "broke" websites by disabling the news in the admin dashboard? If I recall that is like a one line code change. They disabled it because Matt published a disparaging post about WP Engine, knowing that it would show up in the admin dashboards of every wordpress install. That post was about them not being "real" wordpress because they disable post revisions (which apparently they have done for a decade). His own competing managed WordPress service (confusingly named Wordpress.com) disables features as well, unless you upgrade to a higher plan. What a mess. This should have continued to be handled by lawyers and not by using the foundation to disable updates for thousands of sites. What happens to vulnerabilities as a result of this move?
评论 #41653490 未加载
amanzi8 个月前
He&#x27;s lost his mind! Customising the admin dashboard has been something WordPress multisite hosts have been doing for 15+ years! There are tons of plugins on WordPress.org that provide this specific feature. And if you don&#x27;t want a plugin, you can develop it yourself using supported WordPress-provided dashboard hooks: <a href="https:&#x2F;&#x2F;developer.wordpress.org&#x2F;reference&#x2F;hooks&#x2F;wp_dashboard_setup&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developer.wordpress.org&#x2F;reference&#x2F;hooks&#x2F;wp_dashboard...</a><p>Same with post revisions - you can download plugins to customise this, or you can do it yourself with WordPress-supported functionality: <a href="https:&#x2F;&#x2F;wordpress.org&#x2F;documentation&#x2F;article&#x2F;revisions&#x2F;" rel="nofollow">https:&#x2F;&#x2F;wordpress.org&#x2F;documentation&#x2F;article&#x2F;revisions&#x2F;</a><p>Where is the contract that WP Engine signed, that says they must display posts from their competitors calling them a cancer in their customer&#x27;s websites? I&#x27;m really lost for words - I have no explanation for what&#x27;s going on in Matt&#x27;s head.
评论 #41654694 未加载
LegionMammal9788 个月前
&gt; What I will tell you is that, pending their legal claims and litigation against WordPress.org, WP Engine no longer has free access to WordPress.org’s resources.<p>Since when has WP Engine been threatening litigation against WordPress.org or the WordPress Foundation? Their C&amp;D letter [0] was only addressed to Automattic Inc.<p>Perhaps it has to do with the claims of trademark infringement in the counter-C&amp;D letter [1]? But that letter was sent only in the name of Automattic Inc. and WooCommerce, Inc., despite the WordPress Foundation being the ultimate owner of the trademark.<p>[0] <a href="https:&#x2F;&#x2F;wpengine.com&#x2F;wp-content&#x2F;uploads&#x2F;2024&#x2F;09&#x2F;Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf" rel="nofollow">https:&#x2F;&#x2F;wpengine.com&#x2F;wp-content&#x2F;uploads&#x2F;2024&#x2F;09&#x2F;Cease-and-De...</a><p>[1] <a href="https:&#x2F;&#x2F;automattic.com&#x2F;2024&#x2F;wp-engine-cease-and-desist.pdf" rel="nofollow">https:&#x2F;&#x2F;automattic.com&#x2F;2024&#x2F;wp-engine-cease-and-desist.pdf</a>
评论 #41653356 未加载
评论 #41660924 未加载
appendix-rock8 个月前
I have no horse in this race, but this blog post seems like the hot-blooded vitriolic ramblings of a crazy person that can’t mentally separate their commercial and open-source endeavours.<p>The outrage definitely feels at least somewhat ‘put on’ for the sake of publicity. Who cares!?
评论 #41652865 未加载
评论 #41653053 未加载
neya8 个月前
This sets a very dangerous precedent - that this software &quot;sold&quot; as free and open source, free as in free beer and free as in speech is not really free at all. This only exposed the fact that the plugin repository was all along centrally managed and Wordpress has never been truly free all along. That if you tick off the overlords, then you can be banned from this critical central repository of plugins. All this for someone customising the way their admin panel looks like and making some changes they had the right to, in the first place.<p>I think someone should use this as an opportunity to build a better Wordpress clone. You know what, I&#x27;m going to do it. I don&#x27;t care about adoption and market share. I care about freedom. This is not freedom.<p>It reminds me of the WURFL saga that happened a few decades ago for the exact reason.<p>And you know what? Even for such a large, mature product, it is full of security issues, bug and has absolutely poor code quality and poor development experience. Did I mention it doesn&#x27;t even scale without throwing tons of money at it? I will update you guys soon.<p>&#x2F;endrant<p>Thanks.
rob8 个月前
Crazy Matt woke up one day at 40 years old and just decided to ruin his entire reputation and company that he spent over a decade building up.
评论 #41652902 未加载
jwitthuhn8 个月前
Looking forward to them taking a similar action against Wordpress.com for upselling access to the core wordpress feature of plugins.
chuckadams8 个月前
This is not what ceasing and desisting looks like. If Automattic doesn’t fire MM within a week then we know who wears the pants there. A fork backed by real money is starting to look more likely.
评论 #41652869 未加载
评论 #41679898 未加载
lambda-dev8 个月前
&gt; WP Engine wants to control your WordPress experience, they need to run their own user login system, update servers, plugin directory, theme directory, pattern directory, block directory, translations, photo directory, job board, meetups, conferences, bug tracker, forums, Slack, Ping-o-matic, and showcase. Their servers can no longer access our servers for free.<p>Sounds a lot like Android and Google: you can have the source, but good luck without our services!
AlienRobot8 个月前
While I agree with Matt&#x27;s thoughts on Wordpress I don&#x27;t like this sort of public shaming. If you post this kind of thing, it burns bridges that you can&#x27;t mend later. How can the two organizations reconciliate after this?<p>Wordpress wants WP Engine to contribute to the source code because it makes money off Wordpress and uses its servers. I think this is very reasonable.<p>I&#x27;m pretty sure WP Engine could patch Wordpress to use its own infrastructure, so this isn&#x27;t a really as much of a security risk as people claim. Distros have been doing this since forever. This isn&#x27;t much different from a Youtuber getting banned from Youtube. If you build your entire business upon a single point of failure, this kind of thing can happen.<p>But I&#x27;d rather there was a path forward for them. Right now it&#x27;s either 1) Matt gets fired as CEO so WP Engine can continue leeching off Wordpress, or 2) WP Engine has to support its own weight fragmenting the Wordpress ecosystem.<p>Although I use Wordpress I have no idea what people think Wordpress is supposed to be. I love Gutenberg, but everyone hates it, and some hate it because they compare it to site builders instead of WYSIWYG HTML editors. The point is that Wordpress is used by so many websites, both big and small, as a site builder, blogging platform, news platform, and even as a database and shopping platform sometimes, that it&#x27;s impossible to say how it&#x27;s supposed to be used.<p>I think if Wordpress.org makes it clear what are the costs of WP Engine to the project compared to their contributions, it will be easier for people who use Wordpress to understand their side because numbers are neutral.
评论 #41653267 未加载
Kye8 个月前
WordPress supports ActivityPub now, so this is also a spat between two massive AP platforms with apocalyptic potential. Someone needs to get follower migration from WordPress to anything else on the AP fediverse done quick.<p>It&#x27;s inter-instance conflict at incredible scale.
评论 #41654231 未加载
bubblesnort8 个月前
Someone please fork WordPress to e.g. WebPublish and sed -i &#x27;s&#x2F;WordPress&#x2F;WebPublish&#x2F;&#x27; the whole thing and let both of these companies duke it out while we can continue in peace.<p>Much good could come from this.
评论 #41655540 未加载
true_detective8 个月前
I&#x27;ve been paying attention to this drama, is this the correct timeline? Please correct any mistakes.<p>1. Wordpress.org is a not for profit blogging platform that&#x27;s widely used, a crazy figure like 50% of websites are created using this platform. It was created in 2003 and Matt Mullenweg is the co-founder. It&#x27;s community driven and developed and open source (meaning that the source code is freely available for anyone to modify and redistribute).<p>2. Wordpress.com is a for profit website which offers managed WordPress hosting. Wordpress.com is owned by Matt&#x27;s company autoMATTic. Their main competitor is WPEngine.com which is not affiliated with Matt. Wordpress.com was created in 2005, WPEngine.com in 2010.<p>3. Matt used to be a major investor in WPEngine.com, but that&#x27;s no longer the case. In 2024 Matt demands 8% of WPEngine.com&#x27;s revenue for leveraging Wordpress.org (which is, as previously stated, free and open source software). He says the name WPEngine.com is confusing to customers, as they may confuse it with the non-profit Wordpress.org (his own for-profit website is Wordpress.com). What&#x27;s more, instead of paying Wordpress.org they must pay autoMATTic, Matt&#x27;s for-profit company.<p>4. When WPEngine refuse to pay, he delivers a speech at the main WordPress conference publicly shaming WPEngine, saying they don&#x27;t give back. They frack the WordPress eco-system, and urges customers not to use their platform.<p>5. WPEngine issue a cease and desist letter to Matt. Matt sends one back demanding WPEngine stop using Wordpress.org due to trademark violation, and bans them from the platform.
7ero8 个月前
but wordpress.org was built on wp engine
评论 #41663196 未加载