Discord for feeds, lists, mod tools: https://discord.gg/tYuDvuzbVA
Feeds I host (incl. Science 🧪): http://l.bossett.io/w9iM2
he/him
📍 🇦🇺
👾 bossett
📧 [email protected]
I kind of reject the idea that ‘everyone does it this way’ is a good argument when the one that makes the news is npm
I kind of reject the idea that ‘everyone does it this way’ is a good argument when the one that makes the news is npm
not really a generically safe way to work with other people's upstream code & even if we fix *that* we still aren't closer to fixing the 'some packages are just malicious' problem
but... it's also a much clearer line to commercial consequences since security is a 'oh we take the risk and get to move quick and fix it with a press release' v 'oh we take the risk and maybe someone steals our coveted IP'
but... it's also a much clearer line to commercial consequences since security is a 'oh we take the risk and get to move quick and fix it with a press release' v 'oh we take the risk and maybe someone steals our coveted IP'
definitely happens elsewhere but npm is designed to make this almost inevitable
definitely happens elsewhere but npm is designed to make this almost inevitable
but all it takes is one gap that has access to a deployment secret and...
but all it takes is one gap that has access to a deployment secret and...
that way you can handle undefined with an 'API is broken' exception - in case fetch is missing a body property or something
that way you can handle undefined with an 'API is broken' exception - in case fetch is missing a body property or something
until they get annoyed at something and then...
until they get annoyed at something and then...