thats what it looks like to me. It looked like it was trying to continue the handshake while the person was pulling back and the robot was moving forward and stuttered and tripped on the bottom of the barricade causing it to lunge and try and stabilize itself.
That’s what it’s always been. That’s what pays for you to have the ability to send a letter across the country to some rural area for 30 cents. That’s how it works.
I don't know what the actual share of junk mail is for physical or even e-mail, but let's suppose 90% of most people's e-mail in the entire world is spam, should all e-mail providers only deliver email, be it spam or not, once a day?
You can add yourself to the opt-out prescreen list to remove credit card offers for a 5-year period. If you change your mind, you can opt back in at any time.
> replaced it with another plugin that broke people's websites
What makes you think it broke someone’s website? AFAIK they just patched the security issue that wp engine team couldn’t patch because they were locked out from pushing to repo?
Firstly, the security patch was already published by the ACF team, and that wasn't the code that was pushed. This was a package takeover, slug, reviews, users, everything:
People woke up to their website being updated to “Secure Custom Fields”, an alternative (or a fork) that's not fully compatible. Here's one such report from HN:
What Wordpress did is insane, but let’s not spread misinformation. There were no pro features in the free plugin to turn off, they removed advertising for the pro version.
I think it also applies to when managers try to overoptimize work process, in the end creative people lose interest and work becomes unbearable...little chaos is necessary in a work place/life imo...
I kill my desire to work on a lot of side projects by trying to over optimize the parts I’m not going to like doing. I should just do the yucky parts and get past them. But at least nobody is paying me to spiral.
Conclusion: This isn't about OSS, it's about money (and power).
Shamelessly, MM has dug himself a hole. If X is any indication, going forward there are few in the community who will trust him. A leader who isn't trusted is no leaser at all. Evidently he realizes this and is stuck doubling down on stupid. Rinse and repeat.
If feel bad for the people who took off work, went to WordCamp US and they keynote they got was a complete turd.
>If feel bad for the people who took off work, went to WordCamp US and they keynote they got was a complete turd.
I feel like this is a half empty half full kind of situation. Some people might think like you but others might view it as probably the most memorable keynote in Wordpress history (because if all the drama).
If they had an informal development in exchange for server access type relationship then that would qualify as some sort of obligation.
Doesn't really have anything to do with open source though. Haven't seen anything about matt/wordpress.org/Automattic trying to prevent them from using open source code.
It looks like people here are missing the context of the source of the issue between Matt and WP engine. Couple days ago he posted on X that wpengine has similar revenue to automattic, yet doesn’t contribute back to open source as much as they promised to (5 hour per week per employee or something like that). A wpengine employee replied to a post saying that management doesn’t allow them to contribute to Wordpress open source because it doesn’t align with KPI targets. That employee got fired the next day. That’s when Matt’s issue with wpengine escalated.
This seems like a detail that could be covered in a few sentences in the post. In fact it seems central to his argument so it's weird that he didn't. Allegedly it's in the hour-long video, but that's asking a lot.
WordPress cannot relicense; it’s a fork of a GPL project originally (b2) and there is no copyright assignment, so you would need explicit permission from every contributor including the forked project’s.
Further clarification: the project can be relicensed under a compatible license. This approach would mean that new code is released under the new license, such as the AGPL, while the existing code remains under the GPL. It's a little complicated but quite doable.
