[fddrdplktrew]

IRC is great and you can do SSL connections and also encrypted DCC transfers on some servers (Abjects/#moviegods, for example)

[_flux]

However actually establishing those DCC connections in the first place might need some configuration in a typical consumer internet setup?

I've been playing with the idea of adding IRC support to my prototype Matrix WebRTC transfer tool mxrxtx, but I haven't touched that for a while.. And I wouldn't have any use for it anyway.

[dijit]

That's mostly due to NAT.

When we have some more widespread IPv6 adoption we could (and should already) look into supporting IPv6 with DCC, that would make it function properly and dare-I-say would be excellent from a UX perspective.

[Arathorn]

ooh, mxrxtx sounds interesting - is this solving https://github.com/matrix-org/matrix-spec/issues/189?

[M95D]

And this is how good old services, protocols and standards get enshittified. Welcome to HTTP(S) v121.99.5146.

[Avamander]

Except it directly reveals your IP to the other peer. Might as well share a magnet link.

Though I would indeed like direct file transfer for more usual purposes in other chat clients. Would be great with Matrix/Element.

[weberer]

You connect to a server, not a peer. Your client does no uploading.

[fddrdplktrew]

LoL... sharing your IP with a hacked server doesn't really affect me... but when I use magnets links from my home IP, I keep being harassed by Comcast.