3 ms·
Extensions get to modify the same about:config in FF as the firefox internal settings. Some extensions dont work after a year of being undeveloped, because the
by pizzazzaro 8y ago
Extensions get to modify the same about:config in FF as the firefox internal settings.
Some extensions dont work after a year of being undeveloped, because the API changes. Is this really a bad thing? Opensource software uses patching as a "heartbeat" to discern whether a project is still developed or not. Hackers find holes over time, and when devs no longer fill them, the project needs to be left for dead.
Why should browser addons be any different?
I guess its a different philosophy - if the devs leave a browser addon for dead, the users should too.
Once every couple of years, the API changes and cleans out dead addons. Im not sure this is often enough.
But the best addons stay. NoScript. Adblock Plus or uBlock Origin. httpsEverywhere. The best Canvas blockers. These stay up to date.
What is missing?