Demonoid upload ratio not updating

22 Jul

q Bittorrent v2.9.11 was released today to bring a few bug fixes.q Bittorrent v2.8.5 was released today to address a few issues that were reported over the holidays.We are hoping this will facilitate code contributions through merge requests and GIT patches.We need more people contributing code, the development team is way too small at the moment.It is unknown how long I am going to still support it. Thanks to Let's Encrypt and to shiki (forum admin).Also the mainsite is available as a git repo now for (almost) anyone to hack, fix bugs and maybe redesign. q Bittorrent v3.3.10 was released containing hotfixes.Users were unable to change the Web UI username / password from the Web UI which represents a security risk, especially for nox users.

As you can see from the changelog, the project is attracting some new developers, which is excellent news.NOTICE TO PACKAGERS: Read 3.3.8 news and changelog too. NOTICE TO PACKAGERS: Libtorrent 1.1.x series isn't officially supported yet. It also fixes crashes on launch for some Windows setups. On Windows it uses libtorrent 1.0.9 git f716aef5 with commit 45cff5837f7b4af reverted as this one is causing the crashes. As mentioned earlier, there were reports that the forums from a bunch of bittorrent related sites were hacked.This q Bittorent release uses API of 1.1.x that hasn't been released yet. Wait for 1.1.2 release, or build from RC_1_1 branch, or build against the 1.0.x series. As a result we switched off our forum to investigate. We didn't discover any evidence of unauthorized entry. And as you may have noticed from the v3.2.x series, we now have a healthy amount of devs contributing to it. This release finally fixes an obscure "hit-and-run" bug with trackers.Windows users: There is an installer for 64-bit qbittorrent. q Bittorrent v3.3.4 was released after a long time with huge changelog. You'll see a graphic glitch when hovering over the "plus" sign in the content tree.However, you might experience increased memory usage due to this. It is a known problem but Qt 5.6 brings fixes that justify using it despite the graphic glitch.