| ▲ | hypfer 2 hours ago | |||||||
You do realize that the people relying on the service also get served wormable malware, right? The service is already disrupted. It is not that a disruption could be _avoided_. The discussion makes no sense. ___ Hell, even if I would be completely wrong in that assessment (not sure how, but let's assume that's the case) You can still put up a banner. "Hey, FYI: We're under attack". If not right away, then at the very least the moment media reports on it. And if media reported wrong, the banner says "Don't worry people. Media got it wrong." | ||||||||
| ▲ | Tharre 2 hours ago | parent [-] | |||||||
> You do realize that the people relying on the service also get served malware, right? The service is already disrupted. Huh? No they don't. I'm not sure what part of the attack your misunderstood, but most people are going to be completely unaffected by this. None of the infrastructure or anything like that got compromised. I updated my AUR packages 2 hours ago, and didn't get served any malware. Again, there's probably some kind of malware on npmjs at any given time. You don't just shutdown the entire server because of that, that's madness. | ||||||||
| ||||||||