Hello Nikolay,
First, thank you for creating and maintaining RatioMaster.NET. It has been a great tool.
However, as the current version (0.43) is quite old, it is currently struggling to work with modern private trackers. I would like to request an update to address the following critical issues:
-
Lack of Modern HTTPS / TLS Support:
Many modern trackers now strictly enforce HTTPS and are protected by Cloudflare. When RatioMaster tries to connect, it often fails with the error: 400 The plain HTTP request was sent to HTTPS port or An established connection was aborted by the software in your host machine. The application needs to support modern TLS protocols (TLS 1.2 and TLS 1.3) and Server Name Indication (SNI) to successfully communicate with these trackers.
-
Outdated Client Emulations:
The current client simulations are very outdated (e.g., uTorrent 3.3.2, which is banned on almost all modern private trackers). Using these old clients immediately flags or bans user accounts. We desperately need updated .client files for modern and widely accepted BitTorrent clients, such as:
- qBittorrent (v4.3.x, v4.4.x, v4.5.x, v4.6.x)
- Transmission (v3.00, v4.0.x)
- Modern versions of uTorrent/BitTorrent.
It would be amazing if the project could be revived or updated to support these modern web standards and client emulations so it can be safely used again.
Thank you for your time and effort!
Hello Nikolay,
First, thank you for creating and maintaining RatioMaster.NET. It has been a great tool.
However, as the current version (0.43) is quite old, it is currently struggling to work with modern private trackers. I would like to request an update to address the following critical issues:
Lack of Modern HTTPS / TLS Support:
Many modern trackers now strictly enforce HTTPS and are protected by Cloudflare. When RatioMaster tries to connect, it often fails with the error:
400 The plain HTTP request was sent to HTTPS portorAn established connection was aborted by the software in your host machine. The application needs to support modern TLS protocols (TLS 1.2 and TLS 1.3) and Server Name Indication (SNI) to successfully communicate with these trackers.Outdated Client Emulations:
The current client simulations are very outdated (e.g., uTorrent 3.3.2, which is banned on almost all modern private trackers). Using these old clients immediately flags or bans user accounts. We desperately need updated
.clientfiles for modern and widely accepted BitTorrent clients, such as:It would be amazing if the project could be revived or updated to support these modern web standards and client emulations so it can be safely used again.
Thank you for your time and effort!