Re: Helping ensure privacy + security

[email protected] Sat, 5 Dec 2015 10:25:20 -0800 (PST)
Newsgroups gmane.comp.mozilla.devel.plugins
Message-ID <[email protected]>
This thread is chasing its tail and not getting anywhere.

The suggestion of manually enable and disable plugins is micro-management. You can see it as a form of nagging.

I've seen this sort of technique used to annoy users in to not doing it at all because for some reason the company don't want users to do it. Usually it boils don't to money.

Basically it's a form of manipulation technique.

One form of this is Chrome's nagging message when you have custom extensions enabled. Google say it's for "security reasons" but that's just bullshit. They want to control extensions development via their web store. Whatever their hidden reason for it, it's bad.

Excuse the half-rant.

Lets avoid more circular argumentation and wasting of time.
Let me blunt. It's simple, either you revert the change or say you will refuse to do it. So we can move on.

To say you removed it because of "extra complexity" is a weak excuse. After all will not the code be removed anyway when the big change happens, if I understand it correctly. So why the hurry of removing that code now?
I fail to see a valid point here based on this thread.

Excuse my maybe somewhat harsh direct tone.