this post was submitted on 24 Oct 2024
245 points (96.2% liked)

People Twitter

5398 readers
801 users here now

People tweeting stuff. We allow tweets from anyone.

RULES:

  1. Mark NSFW content.
  2. No doxxing people.
  3. Must be a pic of the tweet or similar. No direct links to the tweet.
  4. No bullying or international politcs
  5. Be excellent to each other.
  6. Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician.

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

I think this whole spat is about wordpress.com not .org

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago)

Mullenweg has been blocking WP Engine hosting’s access to .org resources, and even stripping them of access to plugins they distribute there. Not the biggest fan of WP Engine from what I saw in their Advanced Custom Fields plugin buyout (they messed with the existing licensing and focused on monetizing the crap out of it), but things aren’t alright in the WP universe.

[–] [email protected] 1 points 2 months ago (1 children)

I specified org because that's what's in OP, but honestly my comment is the same either way. :D

[–] [email protected] 1 points 2 months ago (1 children)

Don't wp updates and plugins only come from one of the 2? Anyway I'm pretty sure they're just mad that wpengine uses bandwidth from the wp update infrastructure without paying instead of hosting their own update infrastructure, which basically means that selfhosters / individuals are not the target. That said it still sounds like the dude is being hella petty about it.

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

I agree, and after posting that I did dig up this article which helped me a little to understand FWIW: https://www.theverge.com/2024/10/4/24262232/matt-mullenweg-wordpress-org-wp-engine