I think you fundamentally misunderstand my message.
The point I was trying to get across is this:
Companies do bad things, sometimes intentionally, sometimes by accident, and sometimes because they were misguided. Companies also do good things, sometimes intentionally, sometimes by accident. How are we, as users, able to communicate our thoughts with the company in question in these cases?
One method is by calling out the negatives and applying pressure so that, hopefully, the company feels some obligation to act or risk user exodus. This is an example of what you are doing - and it is a valid way of communicating displeasure with a company when they have made a decision the users don't agree with. Negative reinforcement absolutely has its place.
However, an often forgotten method of communication is positive reinforcement. This is how we can tell a company "Hey, good job on this specific thing. It's in a direction we would like to see you keep moving in.". This signals to the company that they are on the right track and, hopefully, encourages them to continue developing that way.
In the specific context of Mozilla, this means that I try to encourage them when they do positive things (blocking fingerprinting) while still expressing my displeasure over the certificate fiasco and other issues.
However, my original post was not meant to be read only in the context of Mozilla, nor was it meant to be read in a way that makes you think that you cannot also raise your concerns. There is a time and place for both positive reinforcement and negative reinforcement. It just seems like people forget about the positive one.
The point I was trying to get across is this:
Companies do bad things, sometimes intentionally, sometimes by accident, and sometimes because they were misguided. Companies also do good things, sometimes intentionally, sometimes by accident. How are we, as users, able to communicate our thoughts with the company in question in these cases?
One method is by calling out the negatives and applying pressure so that, hopefully, the company feels some obligation to act or risk user exodus. This is an example of what you are doing - and it is a valid way of communicating displeasure with a company when they have made a decision the users don't agree with. Negative reinforcement absolutely has its place.
However, an often forgotten method of communication is positive reinforcement. This is how we can tell a company "Hey, good job on this specific thing. It's in a direction we would like to see you keep moving in.". This signals to the company that they are on the right track and, hopefully, encourages them to continue developing that way.
In the specific context of Mozilla, this means that I try to encourage them when they do positive things (blocking fingerprinting) while still expressing my displeasure over the certificate fiasco and other issues.
However, my original post was not meant to be read only in the context of Mozilla, nor was it meant to be read in a way that makes you think that you cannot also raise your concerns. There is a time and place for both positive reinforcement and negative reinforcement. It just seems like people forget about the positive one.