The private trackers should already be familiar with them, should be enough to just mention the new release version.
Explicitly, though, I believe it is -qB31A0-<12 random bytes>
Explicitly, though, I believe it is -qB31A0-<12 random bytes>
The bittorrent protocol specification for a peer id requires that it be twenty bytes in length exactly, so as "-qB31A0-" is only eight characters (bytes) it requires twelve 'padding' bytes.
Also some Windows 7 users experienced freezing of the GUI. We tracked it down to a specific commit in boost 1.56. So until boost fixes it, I am going to use boost 1.55 for Windows releases.
I personally didn't had any problems with v3.1.10 with boost 1.56 either while im a very active user. There were few threads on Github about it, some users with Windows 7 had UI hangs, freezes and things like that and probably had to do with 1.56.
Did something change in the user agent string between 3.1.9.2 and 3.1.10/11 (besides the version number, obviously)? I'm a member on one pair of sites that uses the user agent string to whitelist clients and for some strange reason 3.1.10 and 3.1.11 are giving them fits trying to whitelist the client. They are looking at moving to the peer id in the future but right now there seems to be something strange with the user agent string.... From the execution log just to make sure I'm talking about this right: HTTP user agent is qBittorrent v3.1.11