- cross-posted to:
- technology@beehaw.org
- cross-posted to:
- technology@beehaw.org
Local man sets career on fire.
I have to admit - I’ve struggled to follow this, mostly because every player is called the same damn thing. There’s the website, and the software, and the standard, and they’re all named WordPress, except it’s actually two websites named WordPress, and WP Engine isn’t about the WordPress engine, it’s another website. But it sounds like this guy fucked up in several distinct directions.
F this guy. He’s only causing more work and I hate working.
Haven’t dived too deep in this case. But aren’t WP engine leeching the open source project without barely contributing back to the OSS project?
This is so frustrating as a -very- longtime user and proponent of WP and a current WPE customer. Mullenweg is coming across as petty and out-of-touch with his user base.
Holy crap he is just continuing to build the case against him. His own for-profit automattic’s plugins have built in upsells and add additional data harvesting code that you can’t opt out of while you use them.
He just keeps treating the non-profit .org stuff and his Automattic for-profit as interchangable.
It’s time for the community to find a solution for distributed update servers that at most only rely on Mullenweg for hash checking to prevent tanpering. This is blatantly just a vendetta now.
It’s time for a fork that’s not under hostile control.