4 ms·
It's about revision history, as Matt laid out here: https://wordpress.org/news/2024/09/wp-engine/ https://wordpress.org/news/2024/09/wp-engine/ However, disabl
by GavinAnderegg 2y ago
It's about revision history, as Matt laid out here: https://wordpress.org/news/2024/09/wp-engine/ https://wordpress.org/news/2024/09/wp-engine/
However, disabling revision history is a setting offered as part of WordPress: https://wordpress.org/documentation/article/revisions/#revision-options https://wordpress.org/documentation/article/revisions/#revis...
I'd argue that WordPress.com, the paid hosting platform that Automattic operates, is more of a "hacked up, bastardized simulacra of WordPress’s GPL code". By default you can only load a subset of themes or plugins and only if you choose the Business plan or higher. This seems like a bigger issue than having revisions turned off with a WordPress-provided setting.
It also seems a bit rich to be offering a product using the GPL license and then being upset that people make changes to it?
- nchmy 2y agoIts not about revision history. That's just one of 429 contradictory reasons that matt has given for why he's doing this. Dont take ANYTHING that guy says at face value - he's a psychopath Youre absolutely right though - WP dot com is by far the worst offender of his own standards.
- dylan604 2y agoat some point the disagreement about revision history will be settled through revisionist history
- AdamJacobMuller 2y agoRevision history is the only fig leaf here though about wp-engine being "bastardized wordpress" ? I suppose I understand the argument about wp-engine using significant wordpress.org resources has some merit (but is entirely unrelated to the bastardization argument) if wp-engine is just fetching things like wordpress updates and plugin lists and plugin updates, etc, all directly from wordpress.org servers on a per-blog basis but I find it hard to believe that wp-engine doesn't cache or have their own layer for that.