hmmmmm happy, only partially ;) (But that is because IMHO they are network bits and thus I would prefer megabits/sec instead)
Personally, I would also be OK with changing it to bits. However, it might lead to confused relay operators who expect bytes because this is also what tor's bandwidth options use. I wonder what arma and karsten think.
There is another option that solves this: report both values (MB/s and MiB/s).
The only thing to change then is the graphs, better to resolve that by having a toggle somewhere that allows one to pick between bytes/s and bits/s as these take quite a bit of screen estate.
Personally, I'd prefer bits over bytes, too. But as a developer I prefer whatever is least confusing to users. IMHO that means trying to be consistent with the rest of the Tor world, so count in bytes, not bits.
And making this a user choice, only because developers don't know what's best, seems like a bad idea, too. This is also non-trivial from a coding POV, I'd guess.
I'd say let's close this ticket and save the discussion for a $beverage at 30C3. :)
I think that on this thread everybody is favouring bits actually. Thus just showing bits might be the way to go and then make a note that these are bits, not bytes as seen in Tor.
This is also non-trivial from a coding POV, I'd guess.
Should not be too tricky right, just have a toggle ?units=bytes or ?units=bits
and default on the one that we want to standardize on.
I'd say let's close this ticket and save the discussion for a $beverage at 30C3. :)
Unfortunately C3's are incompatible with this family thing hence I am not able to attend that.... though CCC-folks are typically behaving like family in their good ways ;)