31–40 of 112 posts
How can this work without a a server? You surely need a third party to traverse NAT.
It's using WebRTC's P2P. It does require internet but the middleman is absent in file-sharing.
Earlier quoted context omitted.
Hmm thanks, so that says: > To broker connections, PeerJS connects to a PeerServer. Note that no peer-to-peer data goes through the server; The server acts only as a connection broker. > If you don't want to run your own PeerServer, we offer a free cloud-hosted version of PeerServer. So I suppose there's still a server, but it's shared and run by two folks based on donations: https://peerjs.com/peerserver
Without data going through the server it should be pretty cheap to host, right?
Earlier quoted context omitted.
What is the Gnome equivalent? If you mean GSconnect, that's an implementation of kde connect. I think kde connect has some CLI tools, but they're not super ergonomic. For CLI stuff, I usually just run the python http server or woof and make a QR code with the URL.
What about sharing from your phone to your laptop?
> without involvement of any server > bypassing the need for centralized servers I don't follow this part... it's using a centralized server to serve the web app, which could easily serve JS code that steals confidential data right?
It can not do anything without your permissions. All websites are well scoped and run in their private environment in a web browser.
How can this work without a a server? You surely need a third party to traverse NAT.
Earlier quoted context omitted.
It's using WebRTC's P2P. It does require internet but the middleman is absent in file-sharing.
WebRTC's P2P does require servers; and sometimes even a middleman (TURN). OP wrote about it in https://dikshantraj2001.medium.com/nat-stun-turn-and-ice-466...
> without involvement of any server > bypassing the need for centralized servers I don't follow this part... it's using a centralized server to serve the web app, which could easily serve JS code that steals confidential data right?
That is true, but unless you develop an application yourself, it is always coming from somewhere else. Web apps are better than native apps from a security perspective. Browsers have fairly decent built-in debugging tools that you could use to verify that data isn't being uploaded to a 3rd party. On the other hand, to do the same with a native application you would need to use a separate network protocol analyzer app…
Not saying native apps are universally better, but I do think their treat model tends to be a better match for encrypted messaging. This comment on Signal explained it well: https://community.signalusers.org/t/google-to-retire-chrome-...
> without involvement of any server > bypassing the need for centralized servers I don't follow this part... it's using a centralized server to serve the web app, which could easily serve JS code that steals confidential data right?
Didn't get the part of steals confidential data? It can not do anything without your permissions. All websites are well scoped and run in their private environment in a web browser.
> It is a p2p files and messages sharing platform without involvement of any server. It has end-to-end encryption, ensuring your messages and files remain confidential.
However the clients get the JS code from the web server. Since you control that server, you can change the code to disable the encryption, or send a copy of the messages somewhere else. You can even make the server give specific people / IPs one copy of the code and others a different copy.
Hence my point is there is a trusted centralized server involved.
Earlier quoted context omitted.
Didn't get the part of steals confidential data? It can not do anything without your permissions. All websites are well scoped and run in their private environment in a web browser.
I mean the data people send through the app. You say: > It is a p2p files and messages sharing platform without involvement of any server. It has end-to-end encryption, ensuring your messages and files remain confidential. However the clients get the JS code from the web server. Since you control that server, you can change the code to disable the encryption, or send a copy of the messages somewhere else. You can eve…
Looks good but any plans to make it open source? Similar open source solutions exist like: - https://pairdrop.net/ - https://wormhole.app/ - https://www.snapdrop.net/ How does this compare?
Yes will make it open source in future. Just need to clean the code a little bit and make few more changes.