No! There's a very similar discussion in #9920 (moved). I still disagree about writing "KBytes" instead of "KB" for the reasons stated in that ticket. To be extra precise, it should be "kB/s", not "KB/s". That's also why the "k" in the graph is correct. For more details see also http://en.wikipedia.org/wiki/Data_rate_units
If everybody in the world knew what a kB is, we wouldn't have the constant fights over the torrc config lines, the man page lines, etc.
There are two camps in the world -- those who think things are obviously and always measured in bits, and those who think things are obviously and always measured in bytes. And they repeatedly refuse to realize that the other camp exists.
I'm all for making things as clear as possible. But using a unit that doesn't exist ("KBytes") when there's a standard unit that exists ("kB" or even "KB", though the latter hurts a little) seems wrong.
How about adding tooltips to Globe? Pretty much everything on the Globe details page could use some additional explanation. The tooltip here could be the same as the one Atlas uses: "Bandwidth that the bridge is willing and able to provide in bytes per second".
How about adding tooltips to Globe? Pretty much everything on the Globe details page could use some additional explanation. The tooltip here could be the same as the one Atlas uses: "Bandwidth that the bridge is willing and able to provide in bytes per second".
Here's a build that adds tooltips on relay and bridge detail headlines: