back
3 comments
Thanks. Just installed Consent-O-Matic. I avoided it earlier because I assumed it consented, but by default it does not consent.
Hrm... Maybe I should be using this instead of I don't care about cookies then, since that isn't recommended
Consent-O-Matic is a bit of an edge case because their last update was more than a year ago and their Github repo looks pretty dead. This makes me not really trust it anymore.
I've had few sites that froze when using it coz it clicked something wrong ;/
Interesting they'd recommend Decentraleyes: its default configuration disabled all HTTP link prefetching, which hurts performance in a way not apparent from the extension description.
Decentraleyes has worse issues than that, it’s been mostly abandoned for 7 years and never covered much [1]. LocalCDN is better, but coverage is still insufficient, it still has no chance of actually preventing a CDN connection more than once in a blue moon. Modern privacy folks don’t recommend tools like this because they don’t really work and they do make your network and timing signature much more unique and fingerprintable.

[1]: https://git.synz.io/Synzvato/decentraleyes/-/tree/master/res...

You should have prefetching off by default tbh
Why?
I seem to remember TamperMonkey being on there but not ViolentMonkey, which I didn't agree with. However, I see neither of them on there. Both are available but not recommended. I wonder what is going on with that.
Probably just resources. Mozilla has to vet each update to give them the "recommended" badge and so they probably focus on the most popular extensions
They should have vetted ViolentMonkey instead of TamperMonkey the last time around.
> Tampermonkey - Rating 4.7 (5,306 reviews) - 760,294 Users

> Violentmonkey - Rating 4.7 (793 reviews) - 164,622 Users

On Google Web Store, it's 11,000,000 users VS 900,000 users.

Their popularity seems different by a magnitude, hardly surprising Firefox/Mozilla would chose to focus on one above the other.

I see GP's point tho. The original Greacemonkey was open-sourced. Tampermonkey was the successor and is proprietary. Violentmonkey came to fix that. I wouldn't be surprised if Mozilla rejected TM because of not being OS and rejected VM because of lack of popularity
I get what you mean, and it'd be cool if "Recommended" was only for FOSS, but I don't think that ever been the case? Probably lots of the "Recommended" extensions are proprietary, from https://addons.mozilla.org/en-US/firefox/search/?promoted=re... you don't get far before hitting one, the 3rd extension already is proprietary out of those, surely more.
I still just use Greasemonkey. What is even the point of both successors on Firefox?
I suspect they no longer recommend either because either can download/execute scripts that Mozilla can't review, and the recommended extensions are reviewed, so they don't want to give users the wrong impression.

I could be wrong, however.

I suspect it’s because it’s a pain to review that type of codebase, and they update it decently often.
FireMonkey is the one to use. Not verified, but that doesn't matter.