All is not well in Wordpress land
-
There's a battle playing out in the world of Wordpress, and it's not pretty. There's a company called WP Engine who provide hosting for WordPress sites, and Wordpress, the underlying wordpress engine (I'm going to stick with lower case now). Wordpress is owned a company called Automattic; I'll leave you to dig into those relationships. Anyway, WP Engine recently sent a cease and desist letter to Automattic to stop making harmful statements about WP Engine. Automattic have responded by sending WP Engine cease and desist letters to stop using wordpress trademarks (the WP part from what I can see, although wordpress previously stated it didn't have this trademarked). Fastforward to the weekend; WP Engine provided a wordpress plugin called Advanced Custom Fields. Apparently there's a security weakness in it which WP Engine have a patch for. Automattic suspended WP Engines ability to publish plugins; took the source code and forked it to create their own version called Secure Custom Fields, and the guy in charge of Automattic has been having a meltdown in public. He's been insulting plugin authors; attacking them, and appears to be banning people from wordpress. It's all very sordid.
-
There's a battle playing out in the world of Wordpress, and it's not pretty. There's a company called WP Engine who provide hosting for WordPress sites, and Wordpress, the underlying wordpress engine (I'm going to stick with lower case now). Wordpress is owned a company called Automattic; I'll leave you to dig into those relationships. Anyway, WP Engine recently sent a cease and desist letter to Automattic to stop making harmful statements about WP Engine. Automattic have responded by sending WP Engine cease and desist letters to stop using wordpress trademarks (the WP part from what I can see, although wordpress previously stated it didn't have this trademarked). Fastforward to the weekend; WP Engine provided a wordpress plugin called Advanced Custom Fields. Apparently there's a security weakness in it which WP Engine have a patch for. Automattic suspended WP Engines ability to publish plugins; took the source code and forked it to create their own version called Secure Custom Fields, and the guy in charge of Automattic has been having a meltdown in public. He's been insulting plugin authors; attacking them, and appears to be banning people from wordpress. It's all very sordid.
I'm going to commission a camera crew to start following open source projects and pitch the footage to TLC for a new reality TV program. I'll be rich.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I'm going to commission a camera crew to start following open source projects and pitch the footage to TLC for a new reality TV program. I'll be rich.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Nothing more entertaining than raging nerds. But again, maybe not. Nobody wants to watch a series involving the likes of a Richard Stallman.
:~ X|
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
There's a battle playing out in the world of Wordpress, and it's not pretty. There's a company called WP Engine who provide hosting for WordPress sites, and Wordpress, the underlying wordpress engine (I'm going to stick with lower case now). Wordpress is owned a company called Automattic; I'll leave you to dig into those relationships. Anyway, WP Engine recently sent a cease and desist letter to Automattic to stop making harmful statements about WP Engine. Automattic have responded by sending WP Engine cease and desist letters to stop using wordpress trademarks (the WP part from what I can see, although wordpress previously stated it didn't have this trademarked). Fastforward to the weekend; WP Engine provided a wordpress plugin called Advanced Custom Fields. Apparently there's a security weakness in it which WP Engine have a patch for. Automattic suspended WP Engines ability to publish plugins; took the source code and forked it to create their own version called Secure Custom Fields, and the guy in charge of Automattic has been having a meltdown in public. He's been insulting plugin authors; attacking them, and appears to be banning people from wordpress. It's all very sordid.
Wait, let me get this straight. Automattic forked the plugin and created their own version, and the guy in charge of Automattic is having a public meltdown? That doesn't make sense to me.
The difficult we do right away... ...the impossible takes slightly longer.
-
Wait, let me get this straight. Automattic forked the plugin and created their own version, and the guy in charge of Automattic is having a public meltdown? That doesn't make sense to me.
The difficult we do right away... ...the impossible takes slightly longer.
Yup. That's pretty much it.
