91–100 of 134 posts
Earlier quoted context omitted.
The web page must be served from somewhere, even if the server it came from really wasn't involved in file transfers. It would be nice to have HTTPS for the client to rule out MITM attacks or the like.
The client can be sent encryption keys, generated by the server, and use them for P2P encryption, so the MITM can be avoided.
Why would anyone use this service when you can just transfer files by temporarely opening a TCP port and starting a netcat listener that you pipe into the file you want? It's as simple as nc -lvnp 1234 > myfile.txt The other party then only needs to pipe the file into a netcat socket from their commandline. nc -w 3 IP Jokes aside I'm intrigued at the "no server involvement". I'm assuming they mean the file isn't tran…
I assume this was inspired by the legendary comment on why Dropbox would fail Gave me a good laugh!
Earlier quoted context omitted.
Wait what? It seems to use WebRTC, how is this even possible without https?
WebRTC only requires a secure origin for APIs like getUserMedia, I believe. Sending data back and forth doesn't seem to require a secure origin at all.
I'm seeing less than 4MBps transfer speeds. I would expect them to be faster? (100mbps wifi = 12MBps speeds).
As an alternative, you could use: https://wormhole.app/
Why would anyone use this service when you can just transfer files by temporarely opening a TCP port and starting a netcat listener that you pipe into the file you want? It's as simple as nc -lvnp 1234 > myfile.txt The other party then only needs to pipe the file into a netcat socket from their commandline. nc -w 3 IP Jokes aside I'm intrigued at the "no server involvement". I'm assuming they mean the file isn't tran…
tar c /data/emulated/0 | nc ...
I can't possibly send all photos one by one manually.
Earlier quoted context omitted.
It's even more worse in the mobile world. I would share a lot of pictures after two weeks holiday with somebody who has an Iphone. I have an Android phone. There is not way to transfer pictures direct from Android to Iphone (holiday location != flat rate). WTF 2021.
Use an app like https://www.lonelycatgames.com/docs/xplore/wifi-share over the local wifi (or make the android a hotspot to connect directly) ?
Earlier quoted context omitted.
> I'm assuming they mean the file isn't transferred through the server but directly (WebRTC?) Why are you assuming so, checking how it works is trivial if you open up the Network inspector. I did so in Chrome, and as I said in https://news.ycombinator.com/item?id=29225472 , uploading happens by doing a POST request to the server, and fetching happens by doing a PUT request, not sure why people keep re-iterating that…
There is WebRTC code in the javascript source. It looks like some kind of POST/PUT code is used to exchange metadata about the files, but the files themselves don't seem to get transferred to the server. Or maybe you're seeing different behaviour from everyone else because WebRTC is not behaving right and you're getting the fallback behaviour? The "with no server involvement" part of the title is definitely wrong, th…
Earlier quoted context omitted.
Not even, the application is making GET, POST and PUT requests to send the file to a /link endpoint which also the receiving side is hitting. How is this even close to being "no server involvement"? It's misleading, because the server is very much involved here. > But I suppose that would be basically impossible on today's internet. P2P is possible on the internet (100% without centralized servers), but it's not poss…
>the application is making GET, POST and PUT requests to send the file Have you looked at the actual payload of the POST/GET/PUT requests? It only contains the WebRTC offers/answers. Actual file transfer is via local WebRTC. The site also claims that it only work for "devices on the same network", so there's no need for any STUN/TURN because there's no wall to punch.
It's like saying you can connect to a domain name like google.com with no DNS involvement, because you only get the address and then the connection is over HTTP.
Contrary to some misleading comments in this thread it is in fact using WebRTC. The crux is that WebRTC doesn't show up in the normal Network tab but if you go to chrome://webrtc-internals/ you will see the action.