this post was submitted on 22 Jul 2023
2616 points (99.2% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

61159 readers
221 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):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
 

looks like rendering adblockers extensions obsolete with manifest-v3 was not enough so now they try to implement DRM into the browser giving the ability to any website to refuse traffic to you if you don't run a complaint browser ( cough...firefox )

here is an article in hacker news since i'm sure they can explain this to you better than i.

and also some github docs

(page 9) 50 comments
sorted by: hot top controversial new old
[–] vox@sopuli.xyz 0 points 2 years ago* (last edited 2 years ago) (7 children)

web env. integrity is not as bad as people make it out to be.
yeah I absolutely agree that it's terrible and also a bad idea (we don't need MORE drm in our browsers, I'm looking at you, Widevine (although firefox worked around it by running drm in an isolated container)), but it's main purpose is to detect automated requests and effectively block web scraping with a drm system (it ensures two things: your useragent can be trusted and you're a real non-automated user), NOT detect ad blockers. It doesn't prevent web pages from being modified like some people are saying.
there's a lot of misleading information about the api as it doesn't "verify integrity" of the web page/DOM itself.

it works by creating a token that a server can verify, for example when a user creates a new post. If the token is invalid, server may reject your attempt to do an action you're trying to perform. (this will probably just lead to a forced captcha in browsers that don't support it...)

Also, here's a solution: Just don't use Chrome or any Chromium-based browsers.

[–] nintendiator@feddit.cl 1 points 2 years ago

(it ensures two things: your useragent can be trusted and you’re a real non-automated user),

Nothing in the current proposals does either of those two things. In particular the second.

load more comments (6 replies)
[–] db2@lemmy.one -1 points 2 years ago (5 children)

How does it impact Chromium?

load more comments (5 replies)
[–] Im28xwa@lemdro.id -2 points 2 years ago (5 children)

There is already a manifest v3 compatible version of ublock origin so can someone explain to me how it gonna end ad blockers?

[–] redcalcium@c.calciumlabs.com 1 points 2 years ago* (last edited 2 years ago) (1 children)

uBlock Origin is already less effective when running in Chrome than in Firefox. For example, it can't detect CNAME cloaking on Chrome, while it can do that in Firefox. When Chrome finally enforce manifest V3, uBlock Origin will be even more neutered in chrome due to limited number of blocking rules.

[–] Im28xwa@lemdro.id 1 points 2 years ago

That's a pretty interesting thing to know! Thanks

load more comments (4 replies)
load more comments
view more: ‹ prev next ›