3 ms·
Webtorrent Use a free signalling server from the webtorrent community. You can skip the torrent part of the implementation and just use the signalling, it's aw
by iod 2y ago
Webtorrent
Use a free signalling server from the webtorrent community. You can skip the torrent part of the implementation and just use the signalling, it's awesome. You can use a libraries like:
https://github.com/webtorrent/bittorrent-tracker https://github.com/webtorrent/bittorrent-tracker
https://github.com/subins2000/p2pt https://github.com/subins2000/p2pt
to get started. For me, I found the protocol is simple enough where I just use small vanilla javascipt implementation to talk to the websocket servers to generate the signalling messages. I wish more people knew about this and realize how easy it can be to bring WebRTC to their applications.
List of some free webtorrent trackers:
wss://tracker.openwebtorrent.com
wss://tracker.files.fm:7073
wss://tracker.webtorrent.dev
---> Usage stats for the last one: https://tracker.webtorrent.dev https://tracker.webtorrent.dev
Some free stun servers for NAT traversal:
stun:stun.cloudflare.com
stun:stun.l.google.com:19302
- catapart 2y agoThank you for this! I knew this shit was done by someone already and I've spent two years resisting the urge to re-invent this wheel. p2pt is exactly what I knew was possible and have been looking for!
- nhkcode 2y agoThis is super cool and almost makes it possible building PWAs that only need a dumb http server to deliver the app as a bunch of static files and still allow users to synchronize data between their devices. It still depends on the tracker but if the user could change the tracker it sounds like it's currently the best way to get clients to communicate with each other without depending on a server provided by the PWA.