finds.dev← search

// the find

subins2000/p2pt

★ 640 · JavaScript · MIT · updated Sep 2025

Use free public WebTorrent trackers as signalling servers for WebRTC apps! 🔥 Make WebRTC apps fast & easy ! 🚀⭐

P2PT piggybacks on public WebTorrent tracker infrastructure to do WebRTC signaling without running your own signaling server. You pick an app identifier, it hashes to an info hash, and the tracker hands you peers running the same app. Works in browser and Node.

Zero-infrastructure P2P: no server to deploy or pay for, signaling is handled by public trackers that already exist and stay up. Chunked message reassembly is built in, so you're not manually splitting large payloads over the data channel. The promise-based request/response chaining makes interactive protocols (games, chat) straightforward to implement. Real working apps in the examples list — P2Chat, WebDrop, Vaportrade — confirm this isn't vaporware.

You're entirely dependent on public trackers staying online, staying free, and not rate-limiting or banning your info hash — you have no control and no fallback. Peer discovery only works for web peers; you can't reach native BitTorrent clients, so the actual peer pool is limited to other browser/Node P2PT users of your specific app. No NAT traversal beyond what the browser's WebRTC stack gives you natively, so two symmetric NATs will fail to connect with no TURN fallback built in. 640 stars and last meaningful activity suggests a hobby-scale project; don't build production infrastructure on it.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →