this post was submitted on 15 Apr 2025
18 points (100.0% liked)
Privacy
1997 readers
278 users here now
Welcome! This is a community for all those who are interested in protecting their privacy.
Rules
PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!
- Be civil and no prejudice
- Don't promote big-tech software
- No reposting of news that was already posted
- No crypto, blockchain, NFTs
- No Xitter links (if absolutely necessary, use xcancel)
Related communities:
Some of these are only vaguely related, but great communities.
founded 5 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well its only an issue for that one specific attack vector.
And in its not unique to dark reader its the same for almost every single browser plugin.
Their is a theoretical solution although I haven't seen much discussion on it. It would be to have a browser that runs 2 instances 1 is a sandbox that is identical across all devices and hardware which runs in the background with all the website code (I'll call it proxy). And one instance that just renders the content of the proxy and passes back clicks and keyboard events (let's call this instance interface). You can then make any modifications to interface that u want without any fear of having it be fingerprintable as all it does is render the Dom of proxy.
Theoretically u could even run proxy on a separate VM or even another computer.
Interesting solution. Although it is hard to know if what you're clicking on the end client is the same thing as on the proxy, because some extensions alter the appearance and positions of elements on the page.
Otherwise it's a very interesting take. ๐
If u where gonna do I u would modify the proxy browser and just pass the click directly to the element itself
I don't understand this.
I imagine that won't feel great on load times compared to my system now though?
Theoretically it should be practically nothing if ur running the VM locally. The ram impact would be a far bigger concern imo.
Ah that makes sense! Ty for insight.