this post was submitted on 11 Oct 2024
47 points (84.1% liked)

Programming

17666 readers
343 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 20 points 2 months ago* (last edited 2 months ago) (1 children)

Unless you fork the WordPress source code, it is hard coded to use Mullenweg's Automattic (his for-profit company) servers for plugin updates. This is not something you can tweak in a config somewhere.

So this isn't charging for support services. The open source WordPress is hard coded to be reliant on the for-profit Automattic servers, because Mullenweg has been mixing his non-profit and for-profit business shit.

This has not been a problem ever before. But instead of handling this in any way that might make sense, Mullenweg turned off the update servers for everyone with no notice when WPEngine rightfully responded incredulously to his sudden demand for 8% of their profit based off some weird claims about copyright that are invalid due to Mullenweg's own chosen license terms for WordPress.

He could set up free and paid tiers based off how much load on his servers people create. He could have the code adjusted to make the update server something that could be configured. He could engage the community to have a distributed volunteer network of update servers and reduce his server load by having his servers only provide proper update hashes to validate the updates were not tampered with.

But instead he's having a very very public tantrum with absurd negative impact to the community of people reliant on this open source software.

[–] [email protected] 3 points 2 months ago

Thank you. That’s the part I was missing.