Actually, @questauthority.bsky.social, doesn't this go some ways into making the 'extortion by damage to a protected computer' claim colorable? He is now threatening WPEngine with inability to fix [on some clients] a 'security vulnerability' he is directly drawing attention to, after all.
this also tied into whether WPEngine unfairly used the WP trademark. So Automatt won’t stop talking on podcasts, on HN, on blogs about how right he is and how the other side is lying, and releasing details that make him look genuinely incapable of being an open source maintainer OR ceo
there’s three key entities at play: WPorg, Automattic, and WPEngine. Automattic and WPorg have a porous boundary between them, insofar as employees of the for-profit company do work for the open source nonprofit and leadership overlaps. Automattic tried to make WPEngine pay tithe to them. Went badly
Apparently, Matt is weaponizing a CVE without notifying WP Engine so they can fix the issue before making the CVE to the public, just to use it as an excuse to get people's sites that can get their sites hacked since it’s used on many WordPress sites. No […] [Original post on sakurajima.moe]
And John Gruber’s @daringfireball post: https://daringfireball.net/linked/2024/10/05/wordpress-automattic-wp-engine - - - Et publication par John Gruber de Daring Fireball. // Publication en anglais seulement //
the whole craic around WordPress, WPEngine and Matt Mullenweg is a bit devastating because I always thought that Automattic was one of the better tech companies :(
