Feross Aboukhadijeh
Feross Aboukhadijeh
@ke7ofi Yes, there's already an API to pipe files to arbitrary destinations. See [`file.createReadStream()`](https://github.com/feross/webtorrent#stream--filecreatereadstreamopts), which returns a node.js readable stream which you can pipe to any writable stream, or process...
I think the right place for this change is in webtorrent in [`lib/append-to.js`](https://github.com/feross/webtorrent/blob/master/lib/append-to.js) so that all users of WebTorrent get this feature!
Sure, I'm happy to review a PR that adds support for Windows.
@mrmrs As a maintainer in a similar situation, let me say: *I feel you!* Speaking from experience, I suggest that you focus on what *you* want the project to be....
> I personally would prefer a "yes" to the first, provided we've got a good way of connecting with the team I'm on the Socket team and I'm happy to...
> One thing I did notice, as a rare side effect at being prone to typos, is that an unknown/bad package name is returning a 500 response whereas I'd have...
I can take a look at what it takes to implement this when I'm in the office on Thursday. From what I've heard, torrent encryption does not offer much in...
Confirmed on 9.0.3.
@goto-bus-stop I think we dropped IE8-10 when it had a similar amount of usage (see: https://github.com/browserify/browserify/pull/1678) but if it makes you more comfortable, I'm okay with waiting until usage has...
Just a quick note that since I sent this PR, IE11 usage has declined from 1.16% to 1.00%. > @ljharb 1% is still 4.6 million people - I'd prefer we...