this post was submitted on 21 Jul 2023
2028 points (99.3% liked)
Privacy
31991 readers
433 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Can someone explain how the server is going to know whether or not the client browser is showing the ad? A stealthy browser would say, "hey yeah send that ad so I can render it to the user" and the server says, "yeah ok" and then . How is the server going to know whether the ad is displayed or not? Don't current gen adblockers not even retrieve the asset? If the asset was retrieved but not displayed, how (if even) can this be monitored?
The point of the proposal is to allow servers to be sure the software (ie browser) running on the device is what it says it is, and take away the ability to spoof what browser you’re running (which is currently fairly trivial).
So if someone makes a browser that doesn’t allow adblockers and always shows ads, the server can do things like only serve content to that browser.
Imho, without hardware support they won't be able to keep up against the hackers. In the end it's software and it's running on hardware outside of the control of the server. There are millions of possible attacks to break/bypass this.
Problem is the effort to find a vulnerability and exploit it is often higher than the effort required to patch it. Because by its nature a browser and the server it talks to are internet connected, Google will be able to revoke keys for older exploited versions at will. As long as it’s well-engineered I think there’s a good chance they’ll be able to keep that secure.
Though I’m sure there will be some successful approaches to ad blocking etc but if something like this gains traction it could completely change the internet. If enough people are running browsers like this then sites could effectively be able to kill off competing browsers that aren’t restricted.
I think the key is to not let it happen in the first place, and boycott browsers that implement stuff like this.
So if we already took down Twitter, and Reddit, how do we kill Chrome?