Feross Aboukhadijeh
Feross Aboukhadijeh
> I think we're actually very in sync already. Agreed! I think there's a real opportunity here, given a few compromises, to prevent further fragmentation in community conventions. > but...
We can fix this by calling `emitter.setMaxListeners()` to `Infinity` internally. PR welcome!
I think that supporting a redis backend is a great idea! Also – can you explain a bit more about how the multiprocess websocket processes currently work? Do you shard...
@breebee Thanks for sharing the link to `aquatic`. However, we can't directly run a tracker inside a browser because browsers can't start TCP listening servers.
I was actually thinking of doing the opposite. WebTorrent Desktop has 100% CPU at startup with many torrents active because we need to create so many `RTCPeerConnection` objects (many of...
Hi everyone, The reason that I initially wrote this to use `{ trickle: false }` is to minimize the amount of traffic to the tracker servers. UDP trackers servers can...
> Reducing the number of listening-but-unused WebRTC connections is good Yep, I see the Chrome errors about this issue all the time now.
@noffle It's not just looking up the *last* npm publisher. It's looking up everyone who had npm publish permission at the time of the last release. As a concrete example,...
This is a neat idea.
Cool, didn't know about this spec. I definitely think that explicit `package.json` is the way to go, but I'll leave this open until that's implemented to see how it goes.