sRGB is pretty useless to me, because regardless of how they are labeled, monitors aren't usually accurate to sRGB. I care about showing files as they are actually most commonly seen, not how it is "supposed to be" but not actually IS. In other words, if 90% of people view so-called "sRGB" files under incorrect conditions for what sRGB is supposed to be, in the direction of being too red, then I want my monitor to also be too red compared compared to what sRGB files should be.I'm simply referring to calibrating you're display so that what you see is an accurate representation of the file.
So calibrating to sRGB is not going to accomplish my goals. It only calibrates me to a make-believe world where everybody actually does use sRGB correctly.
When you calibrate, you're not calibrating to "the internet" or "the printer" - you're calibrating to the sRGB standard (or whatever other color space you choose). Average does not equal calibration.
Effectively, the ACTUAL average of viewing conditions and hardware = some hypothetical separate, new colorspace. Instead of sRGB, you could call it average RGB, "aRGB?" Whatever. My goal is to find or measure that color space and then calibrate my monitor to it.
I am defining "aRGB" as the real average of internet users' viewing. So yes, I am calibrating to the average when i calibrate to that.
I just went away from the PC, and whilst eating thought about this. I had an idea, I don't know if it's valid: All the monitors in the world, display a range of brightness, (and contrast combined), from quite dark to 'really really bright'. So set monitor brightness and contrast to 50% and that's the closest you can get to the majority of users. We know that using the RGB colour model, this is also going to have affected colour saturation. So once it's set 50%, then calibrate your colour. That's the closest you can get to the top of the internet bell-curve, no?
