Hacker News Reader

Comment by karaterobot | Hacker News Reader

I've tried using Wormhole and Filepizza from two devices on my network (a MacOS laptop and a Windows PC) and they just don't work for me. I assume the others use the same approach, and would probably also not work. I'm sure there's some setting I could change on my home network to make them work, but I think the point of the article is that we're looking for a way that a) just works, b) across platforms, c) even if you're a dummy like me.

View on HN

I have used many of these to send files from windows to linux or mac to windows. My point isn't that one of the solutions above is perfect, but that the problem has been tackled in a user friendly way with existing web technologies in a variety of ways. These are very small, often one man projects, compared to something like airdrop for example, and they do 80% or more of what you need them to.

I spent less than a minute searching and found another WebRTC based project.

- Site: https://perguth.de/peertransfer/

- Source: https://github.com/perguth/peertransfer

Imagine what could be built with an actual investment? I don't think the money exists for this type of tech, otherwise we would've seen someone do it in the last 20 years.

Just a sanity check: Did you turn off WebRTC and forget that you did? If you're using Firefox, setting both of the about:config flags "media.peerconnection.enabled" and "media.navigator.enabled" to false disables WebRTC.

UBlock Origin's "Prevent WebRTC from leaking local IP addresses" setting also might interfere even though I don't think it turns WebRTC off. The same applies to Brave's "Disable non-proxied UDP" option for the "WebRTC IP handling policy" setting.

Don't do this is you ever use a VPN to hide your IP while browsing.

Don't disable WebRTC while using a VPN? I thought disabling WebRTC was the safe option.

a) Connection from one port of your external IP address to another port on your external IP address will not work if you are behind NAT that is not set up properly to enable hairpin connections.

b) Local IP addresses to connect to may not be provided by the browser to the Javascript code if there's a setting or extension that disables it.

c) Local router can be set up to prohibit traffic between clients (usually wireless devices). If hairpins don't work, you can't exchange any data between such devices without the help of external relay server, as there is no local network at all.

Other than that, WebRTC promises that two browsers can transfer data directly if they are able send UDP packets to each other somehow.

Reply on news.ycombinator.com