by Guest on 2026/09/26 02:35:21 PM
Please, revert back to SAm protocol for I2P torrenting. I'm getting 200-250 KB/s quite easily in qBittorrent which doesn't even have I2P PEX and I2P DHT. But same torrents performance is worse in Tixati where I'm not even crossing 120 KB/s at all. On top of that, Tixati is so intermittent that it's unbelievable. Torrents reached 120 suddenly and then revert to 50 KB/s and then again to 80 KB/s.
In addition to all this, SAM protocol is being favoured by I2P developers as well as libtorrent developer who has been taking keen interest in making I2P more accessible into torrent clients that are based on libtorrent.
I2P development team looks at SAM protocol as a major driver for growth in upcoming years across languages and platforms (I2P in Go language, I2P in Rust language, I2Pd in C++ language etc) all have chosen SAM protocol as their major driver in their GitHub repositories.
I love Tixati that's why I'm requesting please please revert back to SAM protocol. Thanks.
by Guest on 2026/10/02 01:38:53 PM
qBittorrent I2P support has matured quite a lot so much so that it now supports I2P PEX with new update. I have been I2P torrenting for past few years so I have seen many torrent clients performance over the years. And believe me when I say this, that, Tixati I2P performance has downgraded, when it comes to I2P. I do not know specific reasons but it has degraded in both mixed mode and I2P Mode. I love Tixati that is why I am reporting the bugs in it or else there are many options to explore, where even I2Pd is coming with their own inbuilt I2P torrenting client in the next update.
It is my layman assumption that SAM protocol reversal might solve the issue. I might be wrong and it might be cache, peer selection, peer requests and any N number of reasons, so it is better that we wait for developer to take a look at it and rectify whatever is the issue. But my initial assumption I assume is right with the way things are going in i2p developer world.
