Whenever this discussion comes up I liked to point out that even in the computer industry, prefixes like kilo/mega/etc more often mean a power of 10 than a power of 2:
I gave some examples in my post https://blog.zorinaq.com/decimal-prefixes-are-more-common-th...
Nice page, and nice link to Colin Percival's page too! Let me toss you one example: CDs are marketed in mebibytes. A "650 MB" burnable CD is actually 650 MiB ≈ 682 MB, and likewise for "700 MB" being actually 700 MiB ≈ 734 MB. DVD and BD do use metric prefixes correctly, like you pointed out. Back in the day, I archived my data on CD/DVD/BD, and I planned out my disc burns to have only about 1 to 10 MB of wasted space, so I had to be very aware of the true definition and exactly how much capacity was available for me to use.
They almost always mean power of 10, unless you're discussing RAM, RAM addressing, or RAM pages. (or flash, which has inherited most of the same for most of the same reasons)
> The only few places where binary prefixes are used are to refer to RAM capacity and file sizes, whereas decimal prefixes apply to all other areas and all units (not "only bitrates"): storage capacity, clock frequency, stream bandwidth, baud, pixel numbers, data throughput, processing power
Storage capacity also uses binary prefixes. The distinction here isn't that file sizes are reported in binary numbers and storage capacity is reported in decimal numbers. It's that software uses binary numbers and hard drive manufacturers use decimal numbers. You don't see df reporting files in binary units and capacities in decimal units.
Of that large list of measurements, only bandwidth is measured in bytes, making the argument mostly an exercise in sophistry. You can't convince anyone that KB means 1000 bytes by arguing that kHz means 1000 Hz.