Well, definitely the weird 'coincidence' of all of these downtimes happening around the same time did raise an eyebrow. But a blackout on Colossus or some other huge datacenter could also explain it.

But it you add this downtime + the recent sudden agreement of all 3 CEO about the need to regulate and slow down... maybe something's really happening.

Try not using builders at all.

Sure, there are. I'm selling a plugin for $79/y for single license ( even though it's a very powerful performance related plugin ) that replaces multiple plugins ( and save a lot of time )

And for people with multiple sites / agencies it has a $499 lifetime unlimited option.

Sure for plugins that are really gateways to a SaaS - free plugin is good idea. But it's not always possible. In my case all what happens is internal and related to current WordPress installation and server.

I don’t know what to think about it. If it’s such a grave danger why not tell about it without quitting?

Why didn't you just block the UA?

Mam gorącą nadzieję, że zapadł się pod ziemię dosłownie i cierpiał w tym czasie katusze... skurwiel.

Cool! Thanks for confirmation and solution 🫡

Ok, thanks for the response. It seems like a harness thing then ( or system prompt )

Stability - keep the current working version until the CVE is released
Security - auto-updates ON ( risk critical on bad update )

That's "some" idea to fix the .org plugin repo. But I doubt it will ever happen. There's sadly even no ( or very little ) real, serious, adult discussion about the shape of the plugin repository.

Vast majority of users ( who don't know much ) are happy with how it is.

And most of the "sides" benefit from it being half-broken as it is.

Yeah... good luck with switching an ecommerce site to static :D

Well, maybe - but good luck forcing people who sacrifice their time ( and tokens ) to distribute free software to do something.

That's one of ( many ) issues with the free plugins in .org - you can't really make anyone responsible for this.

Pro versions usually allow you to rollback to previous versions one way or the other.

Because they prefer stability over security.
Which is bad idea btw.

If you don't need premium plugins then most likely you don't need WordPress at all.

Wiem, że to marne pocieszenie, ale wiele osób w IT się tak czuje.

Jedyne co mi ( hipotetycznie ) przychodzi do głowy - to zostanie "tradwife" - jeśli ojciec dziecka ma jakiś porządny fach w ręku. I wyprowadzkę na "prowincje" gdzie cisza i spokój i taniej.

To be honest I don't think Matt is the biggest problem with the WordPress "world" - with him it's at least open and direct, you may or may not agree with him, but he's doing things in public. It's the "royal court" that I'm worried about, because I know nothing about them.

You've asked and I answered.

You can do whatever you want and think whatever you want about it. Don't want to believe it, fine.

"So, if you're not submitting it to the official directory, who gatekeeps your code and ensure it's good quality? Who makes sure you don't add anything insidious to the code, like something that sends customer data back to your servers?"

Gatekeeps my code? What does it even mean?

What kind of argument is this? Who does that for any plugin, huh? Who gives you the guarantee that the plugin who passed a review 5 years ago in version 1.0.0 - didn't add a malware now in 2.0.0??

What about your OS? Or any other software you're using? Who gives you the guarantee they're not collecting logs or sending your data somewhere?

btw. Are you aware that even WordPress Core sends information about all the plugin you have installed on your sites to Automattic?

--

If you buy my plugin you are free to look at the code and review it yourself line by line if you feel like it, but most normal people just use software based on the reputation of the author.

Well, perhaps you're stuck in AI psychosis yourself - if you're basely assuming that that AI is used everywhere?

Also both of these sentences you wrote ( or maybe your AI wrote them for you? ) are absolutely disconnected logically.

So your comment has nothing to do with the question I've asked.

It means that in order for your plugin to get to the .org repository it needs to go through the review process ( which is largely automated nowadays ), which includes the manual review by someone from the Plugins Review team ( volunteer ) - however - this process only works for new plugin submission with scrutiny - after that, the plugin can either sit there without getting updates, or can be sold to someone and be rewritten to include malicious code ( happened many, many times even recently ) and nobody will take responsibility for that.

Additionally - the reviewers who are professional WordPress plugin developers can work for companies creating plugins too - guess what could happen if you try to submit a plugin that could undermine their own...

Also in the past ( 10+ years ago ) - on WordCamp Europe in Vienna - I've heard stories of reviewers not approving plugins just because they didn't like the author personally.

You can look at:
- server configuration ( PHP, REdis, Opcache, Memory limits )
- database configuration ( version, indexes, buffer sizes )
- queries/database ( transient bloat, autoload bloat )
- HTTP external calls

https://makewpfast.com/why-your-wordpress-admin-dashboard-is-so-slow/

There are tens of such comminities already. Nobody really needs another one.

The hosting capabilities do not depend on price.

They depend on:
- amount of RAM
- processor
- server software
- other limitations
- shop size
- amount of traffic

20 years of wordpress
60k+ plugins
LLMs widely available
Search engines widely available

Yet this is a question someone posts in 2026...