948
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Feb 2025
948 points (100.0% liked)
Technology
63082 readers
3198 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
I've used this. The only annoyance is that all the on-screen timestamps remain in UTC because JS has no idea what timesone you're in.
I get that TZ provides a piece of the fingerprint puzzle, but damn it feels excessive.
And automatic darkmode isn't respected, and a lot of other little annoyances. That's why this is so difficult. These are all incredibly useful features we would have to sacrifice for privacy.
Dark mode can be recreated using extensions, although the colors most likely won't be as legible as "native support".
I don't see why a similar extrnsion couldn't change the timezones of clocks.
Additionally, I don't see why the server should bother with either (pragmatically) - Dark mode is just a CSS switch and timezones could be flagged to be "localized" by the browser. No need for extra bandwidth or computing power on the server end, and the overhead would be very low (a few more lines of CSS sent).
Of course, I know why they bother - Ad networks do a lot more than "just" show ads, and most websites also like to gobble any data they can.
Wait is that why my Firefox giving me errors when I try to log into websites with 2FA?