161–170 of 210 posts
Earlier quoted context omitted.
> This update is as minimal as possible to fix the security issue. What is the actual issue? CVE number?
Details haven't been made public yet: https://www.cve.org/CVERecord?id=CVE-2024-9529 Though, Automattic posted publicly that there was a vulnerability shortly after filing the CVE, while simultaneously blocking WPEngine from being able to push a fix to it because they'd cut off access to wp.org
Earlier quoted context omitted.
True; I'm just thinking back to the absolute worst drama I can think of in Drupal land, it all pales in comparison. Most of it was misunderstandings that were subsequently sorted, or like Backdrop just a friendly fork with community connections still intact.
I'm glad but slightly surprised neither Crell nor me counts as worst drama for you. Good? I guess.
I mostly did Drupal stuff with local and regional camps at the time, I was hired at Acquia slightly after, so I remember a lot of pain back then, especially as Wordpress and Drupal were often considered in the same meetings when building small local sites for nonprofits, small businesses, etc.
Nowadays it seems Drupal isn't part of the conversation unless there's a C-suite at the place building the website, it's moved upmarket quite a bit.
Blog post on wordpress.org concerning this: https://wordpress.org/news/2024/10/secure-custom-fields/
Earlier quoted context omitted.
Details haven't been made public yet: https://www.cve.org/CVERecord?id=CVE-2024-9529 Though, Automattic posted publicly that there was a vulnerability shortly after filing the CVE, while simultaneously blocking WPEngine from being able to push a fix to it because they'd cut off access to wp.org
I wonder how many Automattic resources Matt threw at ACF to find a vulnerability to catalyze this situation?
Similarly, this is all to resolve the personal grudge of an exceedingly rich dude who wants even more money.
Earlier quoted context omitted.
There are a lot of other employers that won't make you lie for them.
If you point to any lies told by me, I would love to correct them. No one has told me to come here and defend anyone. I work at a part of Automattic that is isolated from anything WordPress — I don’t have to be here. I am defending values I believe in. I am trying to make sure correct information is out there. You are free to not believe that of course.
Posted this in the other thread: A lot of the comments seem to call out Matt (right or wrong). But that’s the easy thing to do. No one dares address the systemic issue of for profit corporations exploitatively (ab)using open source software. There is a social contract that people should contribute back, and while it’s largely unenforceable, as it should be, when it’s happening on a systemic level something has to be…
A number of people have dealt with the maker/taker issue, for example Dries, the founder and BDFL of the Drupal project: https://dri.es/solving-the-maker-taker-problem I think we're pretty far removed from the original issue of WP Engine and WordPress and people are just trying to deal with the fallout from Matt's nuke-the-entire-ecosystem approach he's elected to take.
That was a great article from drupal. It’s a great idea and really goes along way to help, but we still need more.
This only addresses foss projects that are hosted as an offering. It wouldn’t address how for example the pgp guy basically went broke or just the general amount of pressure maintainers of “critical” foss packages are under and are spread so thin, that it’s always a triage fire and there’s never any room to “level up” with rewrites or full code base audits. And a lot of it comes at a huge personal cost but it just so happens the people often times in those shoes end up being super noble.
Maybe this is a cynical take but year after year it really does seem the software we rely on for modern life is just a house of cards where most cards are solo devs or a handful each doing the task of atlas cus the worlds corporations just don’t give back!
My words will ring true in 10-20 years when most of these people kick the bucket or retire and all we have left will be google’s next android| fuchsia and windows server.
Earlier quoted context omitted.
> Clearly AdvancedCustomFields should have filed a trademark to prohibit Wordpress from fully stealing it. They did: Advanced Custom Fields — https://tsdr.uspto.gov/#caseNumber=98321164&caseSearchType=U... ACF — https://tsdr.uspto.gov/#caseNumber=98321135&caseSearchType=U...
Oh nice. Then WordPress shouldn’t be able to take over without renaming, right?
If you were an insider deliberately trying to tank WordPress, it is hard for me to imagine anything you could do that would be more effective than this.
Earlier quoted context omitted.
This release fixes a separate security vulnerability from the original update.
You are abusing the community for your own gain. Stop!
- Matt
- the people who didn't quit Automattic last week
- _maybe_ the WP core developers who don't work at Automattic, so long as they keep their criticisms to themselves