I use qBittorrent, I have used I2PSnark in the past, and it felt clunky and slow, and it was kinda difficult to use

Idk then, I’ve easily gotten speeds of upto 1.2 MiB/s while torrenting, uploading and downloading, I just downloaded a book from a webserver with wget to test my speed through the HTTP proxy, and I got about 150-300 KB/s throughout the whole transfer, I’m using the default settings of 3 hops, and my router isnt firewalled, no clue what the servers settings are.

Yes, you can take the quantity and length options from the http proxy and just paste it into the socks proxy section, I think tunnel quantity can go up to 16, I recommend 8 for high bandwidth stuff like torrenting, but it will use more CPU and battery, but lowering length from the default of 3 to 1 should help a lot.

No worries, hopefully increasing the tunnel quantity will get you acceptable speeds, I could be missing something, but thats all I can think of besides allowing inbound traffic.

Something I forgot to mention, there is the Java I2P router, its availiable in the default f-droid repo, I havent tested it out on Android, but it has a fancy gui on desktop where everything can be configured, it some blocklists of tor exit nodes and stuff, I think that helps performance, I’m not totally sure tho, I dont use the Java versions, they have too many buttons and switches, and its kinda overwhelming for me.

Increasing the tunnel length add more peers per tunnel, but increasing the tunnel quantity will add more tunnels, which will allow more throughput.

I’ve never used this app, but it looks like its using i2pd, I would look for the i2pd.conf, and change the bandwidth flag from L (32kb/s) to like O (256kb/s) or P (2048kb/s), but performance may still not be very good if your router is firewalled.

But you might just be getting bad peers, the speed of a tunnel will be limited by its weakest peer, I would try increasing tunnel quantity on both sides, and allowing inbound traffic on both routers if they arent un-firewalled already, if possible.

It should definitely be possible to setup NGINX & HTTPS to have your i2p router accessable at that domain, but id recommend just using the ssh tunnel with key-based authentication only, it adds an extra layer of authentication and encryption that cant be bruteforced or guessed.

But I strongly advise against having your I2P router bind to a public ip address with just plaintext HTTP

Ive been torrenting on I2P with qBittorrent for a lil while now, its not as fast as the clearnet, the fastest speed down ive ever got so far is 1.7MB/s, and this was on a torrent with loads of seeders. Its possible to increase your tunnel quantity and lower the amount of hops each tunnel has for better performance, but you will have less anonymity with less tunnel length.

But so far its been nice, there is no need to think about NAT/Firewall, as all peers can communicate with each other, but it doesnt have as much content as the clearnet, so I try to cross-seed what I can. But when im torrenting, I try to go I2P-first, and then fallback on the clearnet if I couldnt find what I was looking for.