stun VS trystero

This isn't true.

In 2017 appear.in published some numbers. They saw ~15% were not able to do P2P. https://medium.com/@fippo/what-kind-of-turn-server-is-being-...

Reading your stackoverflow link my guess is that you aren't using STUN. A P2P connection can't be established without a NAT hole punch.

Also if possible I would avoid the terms `Full-cone NAT` and `Symmetric NAT` they don't do a good job of describing what is actually happening. NAT Mapping/NAT Filtering is the best way to describe it. I wrote a little bit about it here [0]. To see what type of NAT you have try stun-nat-behaviour[1]

[0] https://webrtcforthecurious.com/docs/03-connecting/#nat-mapp...

[1] https://github.com/pion/stun/tree/master/cmd/stun-nat-behavi...

If you test your NAT on the destination via a tool like https://github.com/pion/stun/tree/master/cmd/stun-nat-behaviour, what does it report for mapping and filtering?

This looks exciting and I'm pleased to see more and more frictionless ways of making p2p apps. I've been building a somewhat similar hobby project [1] that aims to connect peers in the browser by piggybacking on open protocols out on the net (BitTorrent, MQTT, Nostr, IPFS, etc).

This project seems to be using Hyperswarm which I've looked at for use as a peering medium but it seems like it's not supported in the browser. I'd love to implement it if that story changes since it's so easy to distribute apps on the web.

[1] https://github.com/dmotz/trystero/

I was going to mention WebRTC! It seems designed for video calling, but there are lots of cool use cases - I recently ran across https://github.com/dmotz/trystero , a dead simple WebRTC library for peer-to-peer multiplayer browser games.

I strongly endorse Trystero (https://github.com/dmotz/trystero) for enabling P2P communication in web apps. It’s open source and leverages public infrastructure for matchmaking.

My attempt to get more out of all my ebook highlights using on-device AI. Click the demo button to try it.

https://github.com/dmotz/trystero

Nice work! Any reason one might use this over https://github.com/dmotz/trystero, you think?

Yes, this is a major issue that I haven't found a real solution for. There seems to be a mixture of iOS Safari bugs and intentional design limitations at play, and I don't know if a fully P2P web app like Chitchatter is practical on that platform. There's an open issue to improve this in Trystero (the networking library that Chitchatter uses), but there may be a limit to how stable iOS will be with WebRTC apps. 😕

You can use Trystero (https://github.com/dmotz/trystero) to cut server costs to zero. That’s what I used to build https://chitchatter.im/, which supports P2P audio and video calls.

WebTorrent is obviously well suited for p2p file distribution, but using a minimal subset of the protocol also provides a nice hack for easily bootstrapping peer connections between web app users. Piggybacking on public mediums already designed to do peer exchange can let you rapidly prototype a WebRTC project without the hassle of running your own server anywhere.

I built a library that explores this idea: https://github.com/dmotz/trystero