How do you solve cgnat?
-
How do you solve cgnat? Even if both devices behind different cgnat?
-
System shared this topic on
-
How do you solve cgnat? Even if both devices behind different cgnat?
there isnt any UI for this yet, but id like to make it so users can input their own TURN/STUN servers as described in the peerjs docs: https://peerjs.com/docs/#peer-options-config
id like to work towards making it so that the frontend and backend and independently selfhostable to suit thier networking config.
-
there isnt any UI for this yet, but id like to make it so users can input their own TURN/STUN servers as described in the peerjs docs: https://peerjs.com/docs/#peer-options-config
id like to work towards making it so that the frontend and backend and independently selfhostable to suit thier networking config.
It doesn't sound as zero-installation as you wrote in other comments.
At this point I could just install wireguard on the server and use whatever filesharing protocol I want. As I do now, but I think I'm not your target audience anyway.
If I would use your server, than it wouldn't be really p2p.
-
It doesn't sound as zero-installation as you wrote in other comments.
At this point I could just install wireguard on the server and use whatever filesharing protocol I want. As I do now, but I think I'm not your target audience anyway.
If I would use your server, than it wouldn't be really p2p.
im pretty sure its zero-installation. its a webapp. you go to a url, then thats it.
with WebRTC, the p2p connections is established between browsers. so i think it has a strong case for being p2p. You would be using your own device to run the javascript in the browser and storage provided by the browser is also from your device.
it will do all the encryption, data storage, etc on your browser using only the resources the browser will provide. I believe the functionality as a result is substancially independent selfhosted and p2p.
-
im pretty sure its zero-installation. its a webapp. you go to a url, then thats it.
with WebRTC, the p2p connections is established between browsers. so i think it has a strong case for being p2p. You would be using your own device to run the javascript in the browser and storage provided by the browser is also from your device.
it will do all the encryption, data storage, etc on your browser using only the resources the browser will provide. I believe the functionality as a result is substancially independent selfhosted and p2p.
You coneniently doesn't include the part where you install the STUN server
-
You coneniently doesn't include the part where you install the STUN server
It's on the todo list. Like I mentioned in the parent post, it's far from finished.