Feross Aboukhadijeh

There are subtle differences between Firefox iOS and Safari. In particular, you can't click on a blob url to trigger a file download in any browser except Safari because WebViews...

@kzahel > (I assume some node.js library provides support Yep, there's an npm package `wrtc` which provides WebRTC support in node.js, but it's difficult to install, doesn't work for windows...

@kzahel > Currently JSTorrent doesn't even do seeding because on ChromeOS there is still the firewall, but this is changing soon and this will actually be viable. Nice – this...

Interesting! The issue with WebSocket connections is that it's not P2P. Some server has to forward all the traffic between peers - which is expensive and carries liability. An installed...

> Pretty much all desktop clients are able to do the NAT/uPnP dance You're right. I hadn't even considered this approach before. The nice thing about using WebSockets is that...

That said, we still need WebRTC for browser-to-browser connections, as well as for clients that don't want to support UPnP and NAT-PMP. For example, a native app like [Playback](https://github.com/mafintosh/playback) would...

Ah, right. Clients would need to present a cert signed by a CA. That sucks...

This is an insane idea, but once [LetsEncrypt](https://letsencrypt.org/) is live, it will be possible to get a free cert. It's possible to issue a cert for an IP address. So,...

@kzahel You can see how webtorrent trackers work here: https://github.com/feross/bittorrent-tracker/blob/master/lib/client/websocket-tracker.js https://github.com/feross/bittorrent-tracker/blob/master/lib/server/parse-websocket.js

What do you mean by testing? Sending normal requests to those servers should be fine -- just don't DOS them. ;)