Maybe. Or maybe Firefox users have sophisticated ads & tracker blocker, sometimes even UA spoofing. Then it really depends on your analytics method, if these users show up at all. You might have a lot of FF users, but analytics tells you otherwise.
RocksDB supports hashing at multiple levels (key, value, files) because Meta also realized the importance of integrity. It also supports verifying them in bulk.
Presumably filesystems built over rocksdb also support this.
It would be easy for competition to reverse engineer the physical layout.
I think it's "secret" because nobody really cares.
Do you care for example how the CPU maps the linear memory space across physical RAM sticks and chips? I recently discovered that there multiple alternatives and BIOS settings which give you some control over this.
You can't cheat physics, so at today's CPU speeds, spinning disk HDDs more closely resemble tape drives than not. You have to pay a significant performance price when moving the read head across the disk surface, moreso when you have to wait an entire rotation for the correct sector to fly under the read head.
Prime95 is my gold standard for CPU and memory testing. Everything from desktops to HPC and clustered filesystems get a 24 hour “blend” of tests. If that passes without any instability or bit flips then we’re ready for production.
In my experience, LINPACK (at least the Intel MKL on GenuineIntel combination) is both quicker and more thorough in finding setups that are not actually stable/reliable.
People learn over time that complex web apps work badly in Firefox, because developers mostly test in Chrome.
So they don't even bother trying it in Firefox.