4 ms·
It would be easier to forgive if this was the first time Mozilla pulled this sort of thing. Instead, we see Mozilla making this same kind of mistake -- i.e. tr
by betterunix2 9y ago
It would be easier to forgive if this was the first time Mozilla pulled this sort of thing. Instead, we see Mozilla making this same kind of mistake -- i.e. trying to turn what is otherwise a great browser into some kind of "platform" for things that do not actually serve users -- over and over again.
It's great that it was pulled, but what about removing the ability to silently install add-ons? Give up the power to make this mistake in the future if you want forgiveness.
- devcpp 9y agoAbsolutely. The whole ordeal reminds me awfully of Ajit Pai's tone as he kills net neutrality, sounding as if everything was fine until net neutrality came along. Although different, this too brushes off this one instance as a mistake, and entirely disregards the rest of the article, not even trying to address or explain the rest of Mozilla's recent borderline malicious behavior. A serious fork is long overdue, if only it didn't take a corporation as big as Mozilla to undo their bad deeds.
- callahad 9y agoI'm just one DevRel engineer on a layover; I'm not the right person to answer those broader questions. Not trying to be dismissive, just trying to engage in the areas where I'm most able.
- betterunix2 9y agoDo you have an insight into whether or not Mozilla will issue an update that removes the ability to push add-ons in this fashion?
- Dylan16807 9y agoBah. This was something that looked spooky but ran exactly zero payload by itself. It implies failed processes inside mozilla, but nothing malicious. I still want a justification of the cliqz thing, sure, but I don't demand it in relation to this.