this post was submitted on 29 Aug 2023
624 points (98.8% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54716 readers
181 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
(according to latest statistics, Firefox would have an even lower share)
My point is: if v3 were effective at neutralizing ad blockers in 75% of the user base, or even 95% since Safari is supposed to get on board too, why are they developing additional countermeasures?
Or has Safari decided to do like Firefox, and still allow full ad blockers?
I reckon that blocking ad blockers isn't some extra countermeasure here. It's actually right in line with what Manifest V3 and that new environment attestation system are all about. They're basically making sure that if you tinker with crucial bits of the JavaScript -- stuff they see as essential (like anti-adblock) -- you won't make it through the attestation and you'll get blocked.
They don't want to block all modifications because that would be a hindrance to many users, for example the visually impaired. However, anything affecting their bottom line will probably be blocked.
How that will affect Firefox? I don't know, maybe nothing will change for us, or perhaps Google will block Firefox altogether. We certainly know they're capable.
@LoafyLemon @jarfil @Honse but they could just as well mark the ads as essential then
Yes, attestation is in line with V3 changes, just that it makes them irrelevant: YouTube's website could some day ask for environment attestation of "no extension using the intercept hooks", or "only the approved ones", and still have the same effect. The fact that they're implementing a server-side anti-adblock now, while postponing V2 deprecation over and over, makes me think the V3 changes are a flop.
Firefox... would likely require Mozilla to play ball and implement similar attestation in an official binary attestable by the OS. Edge too, just so MS doesn't mess with Chrome's binary attestation on Windows.
Safari already has attestation, without extra parameters, but it could be extended:
https://httptoolkit.com/blog/apple-private-access-tokens-attestation/