William Blankenship

Leaving this here for future reference RFC5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) https://tools.ietf.org/html/rfc5128

Again, happy to do the legwork on implementing this if it seems like a sane thing to do.

It would be nice to have `torrent.select` and `torrent.deselect` exposed through the UI along with manually controlling the priority for each file. Something like:  Where the priority is a...

Sorry for missing today's RFC Summary from today's meeting relevant to this PR: > [9] Currently blocked. Concerned about the overhead this will create during installation. Agree w/ this, could...

Hey @isaacs :heart: thank you for engaging! > let's figure out the UX and implementation for validating the npmregistry signatures of tarballs Are we talking about `dist.npm-signature` in the packument?...

Ah that is awesome! I fundamentally misunderstood what those signatures were. This seems reasonable. If you can trust the tarball hasn't been tampered with, modifying a packument gives you much...

> Running a global network of the scale of the npm registry will be impossible to do with just being funded by the community as the costs will be too...

@victorb as promised, circling back to report on cost. Self hosting on cloud providers turned out to be reasonable. Our GCP mirror ended up costing ~$300 to do the initial...

@HeroicAutodidact https://github.com/workshopper/goingnative/blob/master/exercises/am_i_ready/child.js#L13-L19 The line immediately above accessing `.test` checks to see if `binding` is defined and outputs an error. @rvagg shouldn't we be breaking execution when each of those checks...

We can at least avoid the `TypeError` for referencing a value we already know is undefined from a previous check. ``` if(binding != null && binding.test !== 'OK') ```