this post was submitted on 11 Oct 2023
2002 points (98.3% liked)
Technology
59374 readers
7409 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- 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, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Compromise: Develop it as a Plugin and then install it by default. That way people who don't want the feature can easily remove it completely. That approach would likely also reduce the number of Firefox forks whose sole purpose is to remove the new features some consider bloat.
Good solution, perhaps two simple options at browser install: Default / Custom. That way you don't have to uninstall all the stuff at the end.
Probably handle it similarly to how Chrome handles an extension asking for new permissions. It disables the add-on and gives the user a small non-intrusive notification on the options menu. Opening the notification notified the user about the change in permissions and asks them if they want to re-enable the add-on or remove it from Chrome.