For the average HNer, a fertilizer spill is unactionable. There's no digging I can do, nothing I can change. At most I can add it to the big list of things I sh

For the average HNer, a fertilizer spill is unactionable. There's no digging I can do, nothing I can change. At most I can add it to the big list of things I should consider talking to my senators and representatives about. By contrast, the liblzma compromise is immediately actionable and HN is who should be reacting to it. I'd wager that some HN readers got paged this morning to deal with the liblzma compromise. There were debian and other distro maintainers on HN communicating about what they knew, what they were doing in response, and what the average HN reader should be doing. I wouldn't be surprised if a reasonable percentage of HN ran, not walked, to run updates on a potentially compromised Fedora installation. Furthermore, the data was all out in the open (git commit history, mailing lists) and in a format that HN readers are specialized for dealing with. A supply chain attack on openssh isn't just relevant to HN, it's the kind of thing that should be on HN because HN is full of the kind of person that we want to be spending time responding to this incident.