[bewo001]

For p2p, you already have the webrtc data channel which handles all the nasty NAT traversal and DDoS issues. Its browser API should be less volatile now than it has been in the past.

Implementing a WebRTC data channel endpoint in a server is not for the faint of heart, though. You would have to implement a lot of complex RfCs.

[captainmuon]

Yeah, but you need a central server, right? You cannot make a DHT for example, like Kademlia or trackerless Bittorrent.

[bewo001]

You need a way to exchange the SDP message contents between your browser and the remote browser. How you do this is up to you. A central server is just the simplest way to do it.