It is possible & already done, however the point remains, that performance is usually absolutely terrible.
With bad #Torrent seeders it's already slow, now imagine you add #TOR on top of it...
I am far less concerned about exit nodes, actually. If Tor is used as the network layer through which torrent runs, that's all I would be asking for.
Also, I just remembered that this article exists: https://geti2p.net/en/docs/applications/bittorrent
So it seems these folks have at least thought of it... but I am, admittedly, far away from fully understanding i2p. I do intend to learn more about it though and my i2pd router is chugging along just fine. :)
(It says firewalled and low tunnel establishment rate, but that is mainly due to CrowdSec just absolutely cucking some IPs. I've been too lazy to manually exclude some stuff but a lot of IPs get straight up null-routed when trying to access my node, due to CrowdSec adding these blocked IPs to my firewall. I set this up on purpose because I was getting a crapton of traffic on port 22 for my SSH at an alarming rate but I need to have this as a failsafe when nothing else can connect to this anymore...)
Discussion
No replies yet.