sigh. i want xul again. i don't want webextensions.
this post was submitted on 07 Apr 2025
286 points (98.3% liked)
Technology
68432 readers
10963 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
We will have to watch closely how Mozilla implements these standardized consent dialogs, because this could be a devious way of obfuscating from the user whether the app uses their data in acceptable or unacceptable ways. I wouldn't put anything past the new surveillance capitalism friendly Mozilla Corp.
The article doesn't link to the source, which is this post:
Today, our Add-on policies dictate that any extension that collects or transmits user data must create and display a data consent dialog. This consent dialog must clearly state what type of data is being collected and inform the user about the impact of accepting or declining the data collection.
Whilst the policy is a great example of Firefox’s commitment to transparency and protecting user data, it can add significant overhead for developers who want to build on our platform, and it creates a confusing experience for end users who often encounter many different data consent experiences for every extension they install. These custom data consent experiences also increase the time it takes for add-on reviewers to process a new extension version, as they need to verify this custom code is compliant with our policies. We’re simplifying how extensions gets consent to collect data
In 2025 we will launch a new data consent experience for extensions, built into the Firefox add-on installation flow itself. This will dramatically reduce the:
- development effort required to be compliant with Firefox data policies
- confusion users faces when installing extensions by providing a more consistent experience, giving them more confidence and control around the data collected or transmitted
- effort it takes AMO reviewers to evaluate an extension version to ensure it’s compliant with our data collection policies
Developers won’t need to bother with creating their own custom data consent experiences. Soon, developers will simply be able to specify in the manifest what types of data the extension collects/transmits and this will automatically be reflected in a unified consent experience across all Firefox extensions.
I hope they don’t go down the google route and kill manifest v2 in the process.
Firefox's version of MV3 explicitly supports the things that uBlock Origin needs to do. It's not the same as Google's malicious MV3 that was targeted at destroying adblockers.
It would be annoying if they removed MV2, but it wouldn't break things like it did for Chromium.
Good to know. Thanks for the heads up.
I wish they'd bring back proper ui mods. Installing stuff like tabmixplus or paxmod is like jumping through hoops of fire.
i doubt that because if they did it what reason would there be to not use one of the many chromium derivatives out there?
Step 1: Don't remove / completely change extension APIs every couple of years