ava on Nostr: GrapheneOS is popular because it’s privacy-ready out of the box—sane defaults ...
GrapheneOS is popular because it’s privacy-ready out of the box—sane defaults mean users don’t have to harden everything themselves.
Yes, the process you linked to is a stop-gap solution, and thank you for sharing, but having a default toggle in Amethyst to block screenshots, Circle to Search, and similar features (like Apple’s) would prevent accidental data leaks.
You would be surprised how many people still screenshot their keys/seed phrases etc. because they don’t realize Google/Apple scan photos, much less build-in AI screen scanning technology. Not everyone is technically literate, or know much about good OPSEC.
When dealing with sensitive information, basic privacy features should be a default, not a bonus feature that needs the user to enable it—that is the kind of thinking that doxxed so many users messages on Telegram (they didn't know they had to manually enable E2EE and that it wasn't enabled by default).
A built-in toggle (enabled by default) preventing screen access would boost privacy, just like Amethyst’s Tor integration avoids IP leaks when users forget to reenable VPN/Orbot.
To me, this would be a sane default—the same way this app screen privacy protection is enabled by default in Banking apps and privacy messengers. If they user wants to take a screenshot, then they can temporarily disable it, or disable it for good, but in my opinion it should be enabled by default.
Privacy in the age of AI should not be an afterthought or a bonus feature hidden in settings—or worse, non-existent as an in-app setting, or something one has to dig into Google/Apple settings to restrict.
#Amethyst has always put user privacy at the forefront. This feature would not permanently affect UX, it would simply allow users greater control over who and what has access to their data out of the box.
Yes, the process you linked to is a stop-gap solution, and thank you for sharing, but having a default toggle in Amethyst to block screenshots, Circle to Search, and similar features (like Apple’s) would prevent accidental data leaks.
You would be surprised how many people still screenshot their keys/seed phrases etc. because they don’t realize Google/Apple scan photos, much less build-in AI screen scanning technology. Not everyone is technically literate, or know much about good OPSEC.
When dealing with sensitive information, basic privacy features should be a default, not a bonus feature that needs the user to enable it—that is the kind of thinking that doxxed so many users messages on Telegram (they didn't know they had to manually enable E2EE and that it wasn't enabled by default).
A built-in toggle (enabled by default) preventing screen access would boost privacy, just like Amethyst’s Tor integration avoids IP leaks when users forget to reenable VPN/Orbot.
To me, this would be a sane default—the same way this app screen privacy protection is enabled by default in Banking apps and privacy messengers. If they user wants to take a screenshot, then they can temporarily disable it, or disable it for good, but in my opinion it should be enabled by default.
Privacy in the age of AI should not be an afterthought or a bonus feature hidden in settings—or worse, non-existent as an in-app setting, or something one has to dig into Google/Apple settings to restrict.
#Amethyst has always put user privacy at the forefront. This feature would not permanently affect UX, it would simply allow users greater control over who and what has access to their data out of the box.