We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

easy to use, functionally equivalent replacement for cookie monster and noscripts in v57?

  • 5 replies
  • 6 have this problem
  • 1 view
  • Last reply by WhoIsItTo

WhoIsItTo
WhoIsItTo
more options

control of privacy in last set of generations of firefox appears to have gotten more and more difficult. cookie monster was suggested as a way dealing with cookie control, but is no longer being supported. noscript also worked well and is no longer supported. umatrix is too difficult to use and ublock it too weak. suggestions please...

control of privacy in last set of generations of firefox appears to have gotten more and more difficult. cookie monster was suggested as a way dealing with cookie control, but is no longer being supported. noscript also worked well and is no longer supported. umatrix is too difficult to use and ublock it too weak. suggestions please...

All Replies (5)

BelFox
BelFox
more options

Hi WhoIsItTo,

The developer of NoScript announced an update for later today: https://hackademix.net/2017/11/14/double-noscript/

Best regards

WhoIsItTo
WhoIsItTo Question owner
more options

thank you belfox for info on noscript update. i'll install when available. anybody have a suggestion for replacing cookie monster?

Mkll
Mkll
more options

Try this: https://addons.mozilla.org/en-US/firefox/addon/a-cookie-manager/

Mkll
Mkll
more options

Or: https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/

WhoIsItTo
WhoIsItTo Question owner
more options

MkII thank you for your two links. Do you know of other cookie manager addons like cookie monster that filter out the url and prevent the cookie in the first place (or least the cookie from being reported back to the url)?