LibreWolf

3163 readers

1 users here now

Welcome to the official community for LibreWolf.

LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. If you have any question please visit our FAQ first: https://librewolf.net/docs/faq/

To learn more or to download the browser visit the website: https://librewolf.net/

If you want to contribute head over to our Codeberg: https://codeberg.org/librewolf

founded 3 years ago

MODERATORS

fishonthenet@lemmy.ml

How to set timezone without disabling ResistFingerprinting (lemmy.ca)

submitted 4 months ago by streetfestival@lemmy.ca to c/librewolf@lemmy.ml

6 comments fedilink hide all child comments

I recently migrated to Librewolf from Firefox due to Mozilla's recent blunder of covertly adding adware to their browser.

I like the ResistFingerprinting feature for added privacy, but enabling it seems to set my browser time to GMT instead of ET, with most times on webpages (which refer to browser time) ahead by several hours as a result.

Can I define my desired timezone in the browser settings so I don't have to pick one or the other between a correct browser time and better privacy? TIA :D!

you are viewing a single comment's thread
view the rest of the comments

[–] DetachablePianist@lemmy.world 4 points 4 months ago* (last edited 4 months ago)

Thanks! I successfully modified your script to adjust for my local timezone. Definitely seems to work on your example webbrowsertools site, though I still can't seem to make AWS happy. no idea where they're pulling their timezone data from, but it always shows me UTC no matter what (and yes, I followed your @match examples adjusting for amazon - the script triggers, just doesn't fix the time displayed for instance monitoring the way I want).

anyway, thanks for sharing your script. I love it! I'll keep playing around to see if I can figure what AWS actually uses to determine "local timezone".