Mozilla will want to be API-compatible, but there’s nothing inherent to the API that requires the arbitrary content-blocking limitation that Google put in. So, Mozilla will be API-compatible without adopting this shitty limitation.
Manifest V3 isn’t just an arbitrary limitation on numbers; it also includes limitations on allowing the lists to be downloaded dynamically, and on blocking elements on pages dynamically
Interesting, I didn’t know that, but it doesn’t really change anything about my comment. Mozilla can offer APIs in addition to what Manifest v3 offers, allowing extensions that want to do these things to do them. It’s already the case today, for example, that uBlock Origin makes use of additional APIs for more effective ad blocking on Firefox.
Why would they want to stop? This is their fight against adblockers and on Chromium based browsers it’s an effective way so of course they keep pushing. ;)
I don’t want to hear the realistic argumentation of why this is proceeding. I want to live in my fantasy headspace where comments like this can stop superpower megacorps from being assholes…okay? 😅
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
can they please just like… don’t?
That’s what happens in a quasi monopoly. They would suffer no consequences from it and the others like Mozilla would just have to follow along.
Mozilla will want to be API-compatible, but there’s nothing inherent to the API that requires the arbitrary content-blocking limitation that Google put in. So, Mozilla will be API-compatible without adopting this shitty limitation.
Manifest V3 isn’t just an arbitrary limitation on numbers; it also includes limitations on allowing the lists to be downloaded dynamically, and on blocking elements on pages dynamically
Interesting, I didn’t know that, but it doesn’t really change anything about my comment. Mozilla can offer APIs in addition to what Manifest v3 offers, allowing extensions that want to do these things to do them. It’s already the case today, for example, that uBlock Origin makes use of additional APIs for more effective ad blocking on Firefox.
Why would they want to stop? This is their fight against adblockers and on Chromium based browsers it’s an effective way so of course they keep pushing. ;)
I don’t want to hear the realistic argumentation of why this is proceeding. I want to live in my fantasy headspace where comments like this can stop superpower megacorps from being assholes…okay? 😅
Seems like something they can’t stop pushing because … reasons.