this post was submitted on 15 May 2024
71 points (100.0% liked)

Firefox

20363 readers
69 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.


Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner


Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.


founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] JohnDClay@sh.itjust.works 11 points 1 year ago (3 children)

Manifest v3 is the new cookie replacement in Chrome right? Is Firefox also adopting it? I think Google's version helps them monopolize information collection and inhibit add blocking, I hope Firefox's version doesn't do that? What's the benefit?

[–] RandomGen1@lemm.ee 47 points 1 year ago

Manifest v3 is about add-ons or extensions like ad blockers, grease monkey, etc. Manifest v3 gets rid of some features of Manifest v2 that will severely hamper ad blocking. Mozilla has committed to keeping manifest v2 support in addition to v3 as a bypass to this

[–] MrSoup@lemmy.zip 39 points 1 year ago

Firefox ALSO supports Manifest v3.

What's the benefit?

To make extensions made for Chrome easily portable to Firefox.

[–] cyrus@sopuli.xyz 14 points 1 year ago (1 children)

Manifest V3 changes capabilities and meta-data about extensions, including limiting lots of things that worsen the experience for AdBlock Users.

Google's "cookie replacement" is Ad Topics, which collects your browser history and puts it into categories, sending those categories to websites.

[–] Vincent 19 points 1 year ago* (last edited 1 year ago) (1 children)

including limiting lots of things that worsen the experience for AdBlock Users

That is the Chrome implementation; Firefox doesn't and won't impose those limits.

[–] cyrus@sopuli.xyz 13 points 1 year ago (1 children)

As per the MV3 Specification, it is supposed to remove some APIs.

Firefox included them anyways cuz they're not assholes.

[–] Vincent 4 points 1 year ago

I think there's multiple specifications at this point. There's Chrome describing what they're doing unilaterally, and then there's the WebExtension working group that's trying to get alignment among several browsers.