this post was submitted on 14 Sep 2024
64 points (93.2% liked)
Framework Laptop Community
2654 readers
1 users here now
Related links:
- Framework website: https://frame.work/
- Official Framework Mastodon: https://fosstodon.org/@frameworkcomputer
Related communities:
- Buy it for life community: !buyitforlife@slrpnk.net
- Fairphone community: !fairphone@lemmy.ml
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Technically, the color has always indicated the opposite of the expected default.
Passive indicators on switches like this historically have used the color to signify when something is disabled, because normally you expect that thing to be enabled. Look back to old devices with mute and disable switches like the old iPhones, Palm devices, etc. and the color always signified the thing being disabled. The default state is enabled, and the switch is disabling it.
Active indicators like LEDs being used on devices to indicate things like the mic or cam being on are generally newer. But even going back to things like the red recording lights, that's because the expected default state was off, and the indicator was showing it was in a secondary state.
The color in both cases indicates the thing being controlled is in a secondary state, but the expected default state is different in the two scenarios.
I guess the disconnect here is that I expect the default state here to be disconnected. More often than not, I am not using my mic/webcam. So when I do, I change the switch to its secondary state to enable it.
I can definitely see your position on this - and from a security minded perspective, it makes perfect sense. I too operate with mic/camera disabled to be my laptop default.
We just happen to be living in a precedent where the "muted" state by common knowledge is red, so FW would design for the "global" average.