- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
cross-posted from: https://lemmy.world/post/11081020
A great video about the Manifest v3 and how Google is trying to make you view ads.
You must log in or # to comment.
Firefox will be using Manifest v3 or was this just posted in the wrong community?
Firefox will be compatible with V3, but keeps compatibility with V2, unlike Chromium.
Firefox is already compatible with v3, by the way, since version 109: https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/
Please Firefox, when mass migration happens, dont let browser monopoly get into your head and change your policy.
I know the Ff code is open source and others can create forks. But still
I’m running with the fox
Actually manifest V3 is awesome as they reduce the permissions of extensions on the browser, which increases user security.
Main point is to tell that manifestV3 is not invented to kill adblockers. Many youtubers are misinforming users for views.
I can assure you that Google, an ad tech company with a near monopoly on web browsers, has an interest in eliminating ad blockers in the browser that they have direct control of.
Actualpy manifestV3 is awesome as they reduce the permissions of extensions on the browser.
That’s literally what kills the ad-blockers. You should watch the video that’s conveniently linked in the post you commented on, it’s only half an hour long and well researched.
So it won’t kill ad blockers?
Yes. Technically, no, you will still be able to have a very simple ad blocking addon, but for all practical purposes, mv3 will kill ad blockers as we know them today.
It won’t kill adblockers but restrict the dangerous permissions an addon / extension asking for.
One of those permissions allows the extension to display the website differently from how it is received. This iterally prevents ad blockers from doing their thing.
Indeed, but what I don’t get is why on earth do people spew this damn crap about manifest v3 as a whole, when the actual issue is just the removal of
"webRequestBlocking"feature that Google is about to bring along with their implementation of mv3. Why the hell aren’t folks mad about the actual issue but instead just want to be mad about the whole bloody thing, which actually also does bring some very real privacy improvements among other nice things.It’s like passing a bill called “protect the people” that has had an add-on that bans porn nationwide. It’s easy to blame the bill.
Which are those dangerous permissions? It doesn’t change any of the permissions that allows extensions to read all site data, so it doesn’t increase privacy/eliminate data theft concerns
yt link:
https://youtu.be/JeTp0khnWgoHere is an alternative Piped link(s):
https://piped.video/JeTp0khnWgo
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
No thanks.
I haven’t watched the video, but judging by the thumbnail, it’s complete bullshit:
I’m not sure on your take of the link you posted but it quite clearly states the limitations placed on these extensions and how they can be rendered useless by the new rules.
