Transmission

I noticed the issue in the Subject and filed #4991 . This was closed since it was an intentional change to fix #276 . After some thought it seems to me that in #276, Transmission is doing what it's supposed to and the problem was user error (the reporter did say that it could be easily be worked aro...

It does make sense to use binary numbers for file sizes, since some forms of storage (for example RAM) are most naturally built in binary sizes, and it's safe to say that no form of storage is naturally built in a decimal size. And it's perfectly reasonable to measure transfer speeds using the same ...

always binary. How did you find out? If this is true, it goes against the standard computing convention of specifying transfer speeds in SI units. See http://en.wikipedia.org/wiki/Binary_prefixes#Information_transfer_and_clock_rates This wouldn't be a big deal if binary prefixes were used so it was...

There's no reason not to put the extra "i" in where it belongs (for example GiB instead of GB). People who know the difference wouldn't have to guess the meaning anymore, and those who don't would just interpret it the same way and no harm done. And even in computing hardware, it's not sta...

Transmission is currently using SI prefixes for file sizes, and possibly in other places such as transfer rates, even though the intended sizes are binary. For example, when Transmission says a file size is "1 GB", it actually means 2^30 bytes, not 10^9 as the SI prefix implies. The simple...