he/him 
If you had to install an npm package by URL, instead of by registry name, would you mind? eg. $ npm install https://website.com/package.tgz $ yarn add https://website.com/package.tgz
Show this thread
-
sounds like going from domains to ip addresses for websites
I think that's too simplified. It's more like going from a DNS monopoly to a distributed system of DNS servers with their own distribution.
-
-
A distributed system of DNS servers would still have human friendly names. A distributed package naming system with consensus and checksums sounds great. Expecting users to enter full URLs, let alone checksums, seems very optimistic.
-
It would only be for installation. I’m not talking hypotheticals, you can do it today. URLs are human-readable, and everyone copy+pastes from tutorials+GitHub anyway, no typing required. https://twitter.com/sebmck/status/1112056018802884608?s=21 …
This Tweet is unavailable. - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.