MB = MegaByte (1024 KBytes, a Byte is 8 bits)
Mb = Megabit (1024 Kbits)
If you want to refer to Mbps, than you need to say "Mbps" or someone may, understandably, be confused.
Actually, I did write Mb as short for Mbit/s, or if you prefer, Mbps (which is itself short for Mbit/s).
Sorry for the confusion created, I did not do it on purpose, I did not even think about it, and did not expect it to generate a fight
.
For me it was automatic, since we were talking about speed of connection, and a speed is always a quantity divided by time (well, I admit in this case it could be considered more precise to talk about a flux of data, but I am used to talk about speed, since the surface is not considered, only the quantity over time), and by default the time used is second in this context.
I understand it can be confusing for someone not used to it, when writing some formal stuff one as to be precise, but I did not have my "formal hat" on
.
Sorry, I am probably skipping some of the messages that went around, so much Zorlun felt the need to ask people to calm down a bit
, but in case it is useful...
Mbit, Kbit, etc. are the "old", original units, that are on base 2, meaning e.g. kilo is 1024, and Mega is 1024*1024. They are still used by JEDEC, for instance for RAM size, and in general for connectivity speed (digital telecoms/networking).
In order to integrate with the SI, which is on base 10 and more generally used for scientific and technical stuff, were introduced kibit=1000 bit, Mibit or Mib - can never remember the exact writing, I am old school
and feel that has been used too easily by hard manufacturers to "nick" people ;-).
Small k, though big M, is not a mistake, it is because the uppercase K in the SI is the symbol for Kelvin, the absolute scale of temperature.
But you can see the difference in daily life easily.
When you buy an hard disk, even if it is a brand new SSD, the capacity is in reality given with the Mega=10^6 (and not 1024*1024), Giga=10^9 (and not 1024*1024*1024), etc., so when your brand new 1TB disk is seen by Windows, it sees it as 900+ GB, not 1024 GB.
In general you can see the small prints on the disk box where they say that they use the base 10 approach.
Though for the forum here, the most important is when the problem with dForce Zorlun is experiencing will be solved and he will be able to work on the content for the next update (well, I guess he can work on the story and I guess the code, but no images or videos), my bet is for Christmas/start of the new year.