News for hackers. Stuff that matters.
Re:Defending Open Source: Protecting the Future of WordPress by simonw on Thursday December 12, 2024 @03:27PM (#42403027)
I don't think this document has been modified since it was first published around a month ago: https://web.archive.org/web/20241104192103/https://automatti...

(I tried running a diff on the current text v.s. the Internet Archive copy from 4th November and unless I made a mistake there have been no updates.)

Re:Defending Open Source: Protecting the Future of WordPress by _aavaa_ on Thursday December 12, 2024 @04:07PM (#42403332)
Ecosystem, Open Source, and Freedom sure are bandied about quiet freely by the same guy who says “WordPress.org just belongs to me personally", and then unilaterally gets to decide what plugins are available to WordPress users.
Re:Defending Open Source: Protecting the Future of WordPress by Deukhoofd on Thursday December 12, 2024 @04:07PM (#42403334)
Well, all this petty mud-throwing has shown me one thing; I will always pick alternatives over the products Automatticc offers.
Re:Defending Open Source: Protecting the Future of WordPress by navigate8310 on Thursday December 12, 2024 @04:08PM (#42403349)
Here's hoping, WordPress, the software will be spared in this corporate vs corporate.
Re:Defending Open Source: Protecting the Future of WordPress by crote on Thursday December 12, 2024 @03:58PM (#42403247)
Ah yes, the Big Bad Evil private equity firms behind WP Engine, which are completely different from the private equity firms behind Automattic. And those 3 private equity board members at Automattic? Just ignore them, they don't exist - focus on those at WP Engine!

Is WP Engine "evil" and predatory? Maybe, possibly. I haven't seen any concrete evidence either way. Is Automattic evil and predatory? Absolutely! We've seen plenty of evidence of that, and it is very clear that they can't be trusted with Wordpress.

Re:Defending Open Source: Protecting the Future of WordPress by gnabgib on Thursday December 12, 2024 @03:25PM (#42403008)
Small discussion at the time (20 points, 3 comments) https://news.ycombinator.com/item?id=42164923
Re:Defending Open Source: Protecting the Future of WordPress by sgammon on Thursday December 12, 2024 @03:46PM (#42403170)
Completely misleading that "Wordpress runs 40%" of the internet when 6/10 packets are also somehow bound for first-party Google properties like YouTube (I guess that means all traffic is bound for either Wordpress or Google? /s).

I'm not sure anybody cares. Really. Wordpress was relevant like 20 years ago. I will probably get downvoted into oblivion by the community of PHP enjoyers that still exist, and good for you guys, I love that you love Wordpress so much. I don't think any of this will change PHP or Wordpress or the thousands of sites that use it. Matt is spending political capital at an unrecoverable rate and the courts are not going to side with him here, I think.

Re:Defending Open Source: Protecting the Future of WordPress by withinboredom on Thursday December 12, 2024 @03:58PM (#42403248)
I guess it depends on how you count (number of sites vs. number of packets).

In any case, many sites include Google Analytics, so Google gets amplified in the packet metrics. Plus, PHP and WordPress are very different beasts. The PHP community has modernized on some standards that are pretty good (most of the time) while WordPress is stuck in 2008.

Re:Defending Open Source: Protecting the Future of WordPress by sgammon on Saturday December 21, 2024 @02:55PM (#42481832)
Google Analytics is valid web traffic
Re:Defending Open Source: Protecting the Future of WordPress by tedivm on Thursday December 12, 2024 @04:17PM (#42403433)
If you aren't familiar with this drama, please understand that Matt and the Automattic folks have absolutely lost their minds when their attempted extortion of a competitor failed.

One of the things about open source is people use it, and they might even compete against your company. If you can't handle that you shouldn't open source your code. Matt is doing far more damage to Wordpress and open source in general than anything WPEngine has done.

Re:Defending Open Source: Protecting the Future of WordPress by 28304283409234 on Thursday December 12, 2024 @04:56PM (#42403820)
Mama always said: "Once you have given the gift, it is no longer yours to decide what happens to it."
Re:Defending Open Source: Protecting the Future of WordPress by sionisrecur on Thursday December 12, 2024 @04:42PM (#42403701)
What's interesting is that Matt is going only after WPEngine. Other providers making lots of money from WP are off the hook. Maybe, ironically, because they didn't go 100% on WP and diversified into other cms.
Re:Defending Open Source: Protecting the Future of WordPress by bilekas on Thursday December 12, 2024 @04:26PM (#42403525)
Again with this drama. Does this company never learn to just shut up already. They don't like that WPEngine made more money And wanted a piece of pie. Now claiming it's a trademark issue. When it stated that "WP" was not trademarked.

> Matt blocked WP Engine’s convenient access to resources he was under no obligation to provide such as the WordPress.org plugin directory

Just like WPEngine was under no obligation to pay towards Automattic.

I didn't think things could get more petty. It's infuriating and gives open source a bad name. "It's open untill we say so"

Re:Defending Open Source: Protecting the Future of WordPress by Gryadn on Thursday December 12, 2024 @04:35PM (#42403611)
You can't make money off my labor/work. Right decision
Re:Defending Open Source: Protecting the Future of WordPress by sionisrecur on Friday December 13, 2024 @10:12AM (#42409114)
You can if I explicitly give you the license to do so. Like Wordpress did.
Re:Defending Open Source: Protecting the Future of WordPress by amanzi on Thursday December 12, 2024 @07:03PM (#42404712)
On a related note, I see the "I am not affiliate with WP Engine" checkbox has been removed from the WordPress.org login pages now. That must've stung...
Re:Defending Open Source: Protecting the Future of WordPress by ThinkBeat on Friday December 13, 2024 @05:07PM (#42412792)
I had not read this before. It gives me more context than I have been missing.