@rysiek @tbr I know the answer to this, but what if we just delete all of the code in npm and start over?

@craigmaloney @rysiek @tbr I have a better idea. Delete all of it and then do nothing.

@rysiek ....wow, it really is.

Like, "[endless preamble and word salad, and then] First there was this security issue [small-ish, temporary, not relevant for execution], and second [everything is on fire]"
@tbr

@rysiek @tbr

I copy-and-pasted everything before "This vulnerability existed ..." and then did a character/word/line count:

$ wc github-buries-vulnerability-lead.md

22 992 6463 github-buries-vulnerability-lead.md

@tbr You should drink more hot or cold chocolate. It's better for your health. I personally can recommend "Grand Cru Chocolat Froid" from Spr眉ngli spruengli.ch/de/shop/getraenke

@tbr I'll just add that to the long lish of reasons I don't/won't touch node.

@tbr inb4 "Node.js considered harmful" becomes a thing

@tbr JavaScript isn't immune from vulnerabilities, just like every other language.

Sign in to participate in the conversation
Society of Trolls

A nice little Mastodon instance. Mild trolling encouraged (keep it local), but not required. Malicious behaviour is not tolerated. Follow Wheaton's law and you'll be fine.