P2P local file transfer based on WebRTC
pairdrop.net
pairdrop.net
It also supports something it calls "Private Room," which doesn't require the endpoints to be on the same LAN. This also works well, at least with my phone on 5G and the Linux box ultimately connected with DOCSIS.
No idea how many intermediaries, if any, are involved with any of this, and for my normal purposes I don't care at all.
thank konqi for kde connect.
https://www.androidauthority.com/android-quick-share-removin...
(I wonder if this is a demand from the Chinese state, because when Apple modified airdrop it was because protestors were using it to spread ... well read https://www.theguardian.com/world/2022/nov/11/apple-limits-i... )
That one is, apparently, now owned by whoever also owns the zombie brand of LimeWire.
For a demo, go to <https://galene.org:8443/group/public/hn/>. Login twice in two different browser tabs (leave the password field empty). Click on the username of your partner, and choose Send file.
I opened a tab and signed in as "username".
Then I opened another tab and signed in as "username" there, too.
Thus a shared chat exists with two users named "username".
Whatever this is, it is not the path of disambiguation.
Transferring files shouldn't involve that central server, so you'd need to establish a direct connection between the users, and with network topologies those days, it will most likely require a relay between the two. It's not great.
That's exactly what Galene does when a user requests a file transfer.
> with network topologies those days, it will most likely require a relay between the two
We perform NAT traversal by using the server to punch holes in both NATs. Only if that fails (due to a symmetric NAT or to an overly restrictive firewall) do we fall back to relaying through the server.