Honey badger shadow beings.

edit 0: words

edit 1: that is an incredible band name

That’s not true for all sites. If the page is static then it’ll have no clue. If it’s dynamic and running a client-side script to report this info back, and if that information is collected, then I can see how that might be a useful supplement for fingerprinting if the server owner is so inclined. At that point though I’m wondering why a security-conscious user is raw dogging the internet and allowing scripts to run in their browser without consent (NoScript saves browsers).

Even then it’s unclear when/how altering the page to render it differently is commonly communicated back to the server, how much identifying information that talk-back is capable of conveying, and how we might mitigate those collections (wholesale abstinence and/or script control aside). What are the specific mechanisms of action we’re concerned about? This isn’t a faux challenge for the sake of hollow rhetoric. I’m ignorant, find the dialogue interesting, and am asking for help being less dumb. :)

I found some brief and useful discussion in this Privacy Guides thread. Seems like the concern is valid but minimal for all but the most strict/defensive postures.

Trying to validate this myself for Dark Reader without breaking out Wireshark and monitoring some big tech site while I toggle color modes (which I might do later if I think of it and find the time) I see Dark Reader is open source, an Open Collective member, and seems to engender little hand-wringing. The only public gripe I can find is this misguided Orion Browser feedback thread.

Thanks for the interesting diversion!

How so?

This is admittedly a bit pedantic but it’s not that the risk doesn’t exist (there may be quite a lot to gain from having your info). It’s because the risk is quite low and the benefit is worth the favorable gamble. Not dissimilar to discussing deeply personal health details with medical professionals. Help begins with trust.

There’s an implicit trust (and often an explicit and enforceable legal agreement in professional contexts (trust, but verify)) between sys admins and troubleshooters. Good admins want quiet happy systems and good devs want to squash bugs. If the dev also dons a black hat occasionally they’d be idiotic to shit where they eat. Not many idiots are part of teams that build things lots of people use.

edit: ope replied to the wrong comment

deleted by creator

How?

I’m excited to see they’re going fully open source. Looks like the last steps to making the sync server self-hostable are in the works. Do you use their paid service? If so: any complaints or caveats?

Start here: https://nesslabs.com/how-to-think-better This isn’t an endorsement (though I do like ness labs). That article offers practical evidence-based starting points and additional resources at the end.

There are many people/systems/schools that will offer strategies and solutions. Some are practical and effective. None of them are a replacement for learning what it means to think well, learning how to think well, or actually thinking well.

The next step is learning the jargon of philosophy so you can ask meaningful questions and parse the answers (this is true for any new discipline). I recommend reading anything on the topics of epistemology, ethics, and aesthetics, which resonate with you. Then find others to discuss what you’ve read. You do not have to be right or knowledgeable to earn a voice in the conversation: only an interest in discovering how you might be wrong and helping others discern the same for themselves.

If you haven’t read any classical philosophy but are interested I recommend Euthyphro. It’s brief, poignant, and entertaining.

I hope this helps! Happy to discuss further as well.