3 ms·

Wow, the WordPress name is being ploughed into the ground with this sort of behaviour.

• josephg 2y ago
  Well, they banned Wpengine from updating their package in the repository. Then the package maintainers found security problems - which they can’t fix with an update because they’re locked out. It makes a weird sort of sense. Ie, wp.org backed themselves into a corner where they needed to close the security hole. And to do that, they needed to patch it themselves, which in turn requires them taking over the package. It’s shocking, yeah. But it would probably be worse if they just left the (known, publicised) security vulnerabilities in.
  • srmarm 2y ago
    They could have backed down and allowed WPEngine to publish an update or even published it on their behalf. Instead they've doubled down and taken this ridiculous action that undermines the whole wp/plugin eco system. None of this is necessary.
    • pluc 2y ago
      This was engineered and deliberate, they were never gonna let WPEngine have their space back. We called this a week ago: https://news.ycombinator.com/item?id=41751856 https://news.ycombinator.com/item?id=41751856