[jech]

Nice design, but that's the kind of functionality that's best integrated within a chat or videoconferencing application, since within a conference you can be pretty sure that you send the file to the right person.

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.

[felooboolooomba]

No, it's best to write the data on a USB stick and see the person in real life. Ask for ID and do a retina scan. Then you can be pretty sure that you give the file to the right person. Make sure to cryptographically sign the data so the recipient can be sure it's you.

[ssl-3]

I used your demo. It does not do what you say that it does.

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.

[Orphis]

In modern conferencing applications, users are not connected with each other, they are connected with a central server.

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.

[jech]

> Transferring files shouldn't involve that central server, so you'd need to establish a direct connection between the users

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.

[alhadrad]

I don't agree with this.