Conversation

Notices

1. Embed this notice
   David Revoy (davidrevoy@framapiaf.org)'s status on Sunday, 02-Mar-2025 21:52:57 JST David Revoy

   @Yingwu That's exactly where I found it educative to have to be personally facing this dilemma and having to choose.

   Here I decided to allow fingerprinting, because mainly I really like when a blog or website switch to dark mode automatically. Without that, all website were in light theme, and it felt very difficult to me to browse the web like that now...

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Sunday, 02-Mar-2025 21:52:56 JST 翠星石

     in reply to
     @davidrevoy @Yingwu Even though selecting the dark theme would give a whole 1 bit of fingerprinting, browsers that serve the users really allow optionally keeping dark themes even with fingerprinting resistance enabled.
     
     There is one extension that will set a dark theme regardless min you; https://addons.mozilla.org/en-US/firefox/addon/dark-background-light-text/
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Monday, 03-Mar-2025 21:36:10 JST 翠星石

     in reply to

     • LisPi
     @lispi314 @davidrevoy @Yingwu Unfortunately, certain CSS features allow remove endpoints to work out the state of CSS modals, so the CSS standard would need to be changed to allow that.
   • Embed this notice
     LisPi (lispi314@udongein.xyz)'s status on Monday, 03-Mar-2025 21:36:12 JST LisPi

     in reply to

     • 翠星石
     @Suiseiseki @Yingwu @davidrevoy Not selecting it also gives a bit of fingerprinting, ultimately.
     
     Preferably the way to fix this would be for the user agent to not provide the remote endpoint with a way to extract this data at all.