uMatrix: for blocking all kinds of stuff and to see what kind of connections each site uses (usually a ton)
HTTPS Everywhere: to have https everywhere. According to @Jojonintendo this is already integrated into Firefox though, so I might delete it.
Cookie Autodelete: pretty self-explanatory.
Decentraleyes: to prevent websites from loading unnecessary resources.
Privacy Redirect: mostly used to open Youtube links in Freetube, but also to redirect Reddit and Twitter links to libredd.it and Nitter respectively, when needed.
This kind of extensions don’t need several commits every week, for example updating a software once per month could mean that it’s more stable and has less bugs than one that updates every day.
About the feature though, you’re right, localCDN does block a lot more CDN requests
Decentraleyes is not dead, it’s feature scope is just more narrow, meaning it’s reached “product maturity” quicker.
Think of it as running Debian stable vs Arch Linux - Debian isn’t dead it just progresses at a slower and more stable pace than Arch. Slow & steady gives you tremendous stability at the cost of missing out on a few features.
Some people, like myself, prefer stability over fancy new features. I’ve tried LocalCDN, but found it interfered with a lot more websites than Decentraleyes, which is a “set and forget” addon. Not to say the LocalCDN project is bad; its not, its great and I would like to switch back to it at some point; but in my testing, it’s not something I would set for my parents, and found it more of a hassle for myself so I switched back to Decentraleyes.
In Firefox I have:
Decentraleyes is dead, swap it for LocalCDN, an actively maintained fork.
Really? Their repo seems to be fairly active, though.
https://git.synz.io/Synzvato/decentraleyes
LocalCDN supports more CDN resources and other features that Decentraleyes didn’t implement yet. P.S. It works better in Firefox.
Good to know. I’ll be switching to LocalCDN then. I honestly wasn’t aware Decentraleyes had a fork.
Must be recent then. It was stopped for a big while. Either way, as the other commenter said, LocalCDN supports more stuff and works better.
This kind of extensions don’t need several commits every week, for example updating a software once per month could mean that it’s more stable and has less bugs than one that updates every day. About the feature though, you’re right, localCDN does block a lot more CDN requests
You make a good point yeah. However, I believe it went radio silent for a considerable amount of time. Not a big deal though.
Decentraleyes is not dead, it’s feature scope is just more narrow, meaning it’s reached “product maturity” quicker.
Think of it as running Debian stable vs Arch Linux - Debian isn’t dead it just progresses at a slower and more stable pace than Arch. Slow & steady gives you tremendous stability at the cost of missing out on a few features.
Some people, like myself, prefer stability over fancy new features. I’ve tried LocalCDN, but found it interfered with a lot more websites than Decentraleyes, which is a “set and forget” addon. Not to say the LocalCDN project is bad; its not, its great and I would like to switch back to it at some point; but in my testing, it’s not something I would set for my parents, and found it more of a hassle for myself so I switched back to Decentraleyes.