I2P support is now really usable, congrats for the effort.

There are some glitches however:
- Trying to actually use the tunnel quantity parameters (tried 10 and 16 for inbound and outbound) kills the entire I2P feature
- When adding a clearnet magnet link, I expected the tracker to be taken from the magnet URL. Actually the I2P Postman tracker was used with an error displayed.
- When creating a torrent, I used a preset with 3 I2P announce URLs, Postman first. I expected all URLs to be included in the torrent file, but only the second was used, making the torrent unusable on Postman.

In general, Postman is the only usable source for I2P torrents (and a single point of failure) und thus should be included in every I2P torrent by default, until another reliable I2P torrent site comes up.

I think you still somehow believe that torrents are impossible to use without trackers, that everything is required by law to have a catalogue web page on some site, and can't just be copied as hash or magnet. This is not true for almost every client, not just Tixati. You don't have to use the Postman tracker if you don't want to list your torrent into its catalogue.

16 inbound tunnels means you need to have at least 16 peers to download from at any time (probably more to fill the bandwidth). 16 outbound tunnels means you need to have at least 16 peers to upload to at any time (probably more to fill the bandwidth). Given that most I2P torrents are mostly inactive, you need to add quite a lot of them to the client. Needless to say, anonymity goes down the drain with such a vividly active node.

Most people want an interested community to share torrents. On I2P currently Postman has absolutely no viable alternative to reach a significant audience. Of course there are people out there wanting to trade stuff banned on Postman. Those share hashes elsewhere, but this a small minority.

The previous post does not exhibit deeper knowledge of I2P. If I send a message out on an outbound tunnel, there will be at least one reply on an inbound tunnel. A round trip typically goes through > 10 connections. If one of these hops breaks away, the end-to-end connection is broken. So five tunnels put 20% of your traffic at risk, if just one intermediate node goes down. This is why other clients allow 10 or 16 max. tunnels and adjust quantity according to load.

tried it and yes I2P Support has increased quite significantly. Excellent work by developer

the developer just did a whole bunch of work on I2P for v3.37, including udp tracker support.

I am now also able to raise the tunnel quantities to 16, as in BiglyBT.

raising to 16 quantity does not matter if you do not have that kind of load in your torrent,i.e., if you do not have many peers.
Furthermore, raising tunnel quantities increases load on CPU and RAM.
It is better that you stick to defaults - standard and 1 hop - as per your preference - if you are torrenting over I2P Tixati.