zlacker

[parent] [thread] 3 comments
1. nextle+(OP)[view] [source] 2023-07-26 11:17:54
How does this prevent ad-blocking?

If website you visits asks you to confirm that you are a human user from some 3rd party API isn't that same as requiring captcha?

You can still have browser extensions that filter the ads away after the website sends you the final HTML, right?

replies(2): >>stevag+R >>hhjink+u3
2. stevag+R[view] [source] 2023-07-26 11:22:47
>>nextle+(OP)
>You can still have browser extensions

Not if there's only one browser that you're allowed to use, and it's owned by the world's largest advertising company.

replies(1): >>nextle+N1
◧◩
3. nextle+N1[view] [source] [discussion] 2023-07-26 11:28:25
>>stevag+R
How can you prevent modifications of memory when the software is running on hardware I own?

Also what would be the benefit for other companies to agree to have their customers be vetted by Google run API that excludes portion of customers?

4. hhjink+u3[view] [source] 2023-07-26 11:38:37
>>nextle+(OP)
The point of attestation is to verify the integrity of your execution environment. With a "compromised" execution environment, access to websites could be blocked. Presumably, the attestation process would send a fingerprint of your browser configuration to the attester, who would then be able to see whether you're using "compromised plugins," and deny you access by not attesting your browser.

There might be ways to filter away the ads after they've been served, such as memory manipulation, but the problem can't be solved with a plugin anymore, as browser attestion could let websites deny you access altogether if you use a plugin they don't like.

[go to top]