I built a browser-based P2P file transfer tool using WebRTC

https://gist.github.com/SMUsamaShah/fd6e275e44009b72f64d0570... I keep a handy list. Does this stream file directly to disc or keep it in browser cache or memory? In this list I think only web wormhole does that which means it should be able to transfer huge files without any problem. Most tools crash if files are in GBs.

You have some web page material in English, and some material in either Spanish or Portuguese. You might want to check everything twice before posting on HN.

I guess this sort of tool provides a good learning experience for developers or implementing one scratches some other itch, because there are so many one here:

<https://hn.algolia.com/?dateRange=all&query=peer%20file%20sh...>

I love this idea.

But i just tried it in zen browser on fedora 44 and the system hard locked up. I guess I could try chromium next time.

How is it different from https://copypaste.me/ ?

Looks great. How long until it does P2P via Bluetooth?

Like Bump did before it was shut down by Google.

Does anyone know what the actual success rates for webRTC are for like different NAT combinations / nodes in the wild? I'd be curious, I have read a little into it myself but didn't get the feeling it was very flexible compared to something like Tailscale.

Hi, I built a plugin-based P2P socket system from scratch that supports TCP punch, UDP punch, random probe, TURN, and other such systems. It includes a full stack from networking, signalling, and naming, all based on open infrastructure. It's open source and licensed under MIT:

warpgate.io

What happens when TURN is inevitably needed? Many people are behind something like CG or symmetrical NAT with no direct way to talk to each other.

There are no reliable, fast AND free TURN servers (IMO), and even semi-private relays can quickly become overwhelmed or too costly to operate.

[flagged]