There's no shortage in ideas of how to make the AUR easier to moderate. A "quarantine button", an invite system, a request system for adoption similiar to how orphan requests work, code review attestations similiar to cargo-crev, pacing controls similiar to those in discourse.

There is a shortage however of people skilled enough to implement them (with available time to do so).

What we also don't have a shortage of is angry people in comment sections.

▲

hypfer an hour ago | parent [-]

People have all right to be angry if basic responsible adult things like "quarantine the server spreading large amounts of malware" do not happen within the reasonable timespan that passed.

Not even a news. A hint. Nothing. Radio silence.

___

There is a house. It is currently on fire (since over 24h). So far, people have talked about how, conceptually, house fires are bad.

You can still enter the house just fine.

People saying "hey what about locking the door to not trap more people in it" are being shunned for the crime of breaking someones workflow.

The owner of said house is nowhere to be seen.

Passerbys stating "oh my god that house is on fire! get water!" are either ignored or reminded that there is no problem and they should move along.

___

Idk man. I don't think any of this is real.

And I don't even use arch, lol. And after this thing exposed the institutional rot, neither should you or really anyone.

Unless you like ending up locked inside a house fire. I guess they provide warmth in the cold harsh reality of the 2026 internet.

▲

kpcyrd 14 minutes ago | parent [-]

The server actually hosting the rootkit executable is npmjs.com, run by a for-profit company, and they still take about 24h to act on our reports, while reported AUR packages have been processed in about 1-2h by people that work unrelated dayjobs on top of this, to self-subsidize their open source work.

Sorry you're displeased with us not writing blogposts faster on top of all this. The situation is already exhausting enough without people like you.

▲

hypfer 8 minutes ago | parent [-]

Look, man, I understand all that, but pulling the plug is something that takes at most 90s. Let's say 300s to add the "Warning: There is an attack. We're working on it. Systems are down for now" box

After that, you have all the time in the world to prioritize dayjobs etc.

It's not about dropping everything and fixing the root cause. It's just about taking stuff offline so that the immediate danger is mitigated.

That is not too much to ask. It's not "people like me" having weird opinions there.

Shut it down. Then fix whenever there is time to do so.

___

But hey. Finally a statement from someone with some amount of position in the org I guess?

I wouldn't want to be in your shoes for sure, but that's beside the point. Nothing here is unreasonable other than the ostrich-style incident response lack-of-process.

And I don't mean stupid corporate process. I mean "common sense adults are in the room" process. Throw waterbucket at burning server reflex.

___

I mean I can see that your userbase absolutely sucks and could imagine that one would be scared of getting roasted for "interrupting their workflow", but this is not the way.

Their workflow is irrelevant.

As said, I'm all here for maintainer empathy, but only after the fire is put out first.

	▲	Tharre a minute ago \| parent [-]
		[delayed]