Mozilla can’t be trusted to host the addon, so the author is taking on the responsibility of hosting it himself. How is that his fault and not Mozilla’s?
Whether Mozilla acted out of malice or incompetence is irrelevant. The report was false and the findings were incorrect, they have to be held responsible either way.
I’d much rather have them be overzealous and mistakenly block an addon for a few hours, than have them be too lax and approve addons actually stealing data.
Mozilla did apologize, said they were wrong and said they’d correct the issue. The author refused and decided not to put it back to AMO. At that points its on the author that it’s not AMO.
Promises from a for-profit company don’t mean shit. How many times have you seen the “we’ve heard you and we’ll do better next time” routine, only for next time to be the same or worse? They’d promise you the pissing Sun if it meant more dollar signs.
They’re empty words. No company will put out a statement saying “we fucked up, we’re sorry, it’s going to happen again”. Until Mozilla can prove through actions that the issue is fixed, Hill is correct in distrusting them.
This is such a storm in a teacup. Someone making the manual checks at Mozilla fucked up and the situation was quickly admitted. I don’t know what else to wish, other than that the failure wouldn’t have happened in the first place. Sucks that it did. Now what sucks is that gorhill doesn’t want to do put it back but it is what it is, luckily it was just the Lite version.
While I like a juicy conspiracy and fuck the sytsems and all, I don’t think they were lying when they said that they’d put the addon back if gorhill just resubmitted it.
Mozilla can’t be trusted to host the addon, so the author is taking on the responsibility of hosting it himself. How is that his fault and not Mozilla’s?
Whether Mozilla acted out of malice or incompetence is irrelevant. The report was false and the findings were incorrect, they have to be held responsible either way.
I’d much rather have them be overzealous and mistakenly block an addon for a few hours, than have them be too lax and approve addons actually stealing data.
They also removed all previous versions except a very old one with known issues, thus exposing people to more danger than necessary in any way.
Mozilla did apologize, said they were wrong and said they’d correct the issue. The author refused and decided not to put it back to AMO. At that points its on the author that it’s not AMO.
Promises from a for-profit company don’t mean shit. How many times have you seen the “we’ve heard you and we’ll do better next time” routine, only for next time to be the same or worse? They’d promise you the pissing Sun if it meant more dollar signs.
They’re empty words. No company will put out a statement saying “we fucked up, we’re sorry, it’s going to happen again”. Until Mozilla can prove through actions that the issue is fixed, Hill is correct in distrusting them.
This is such a storm in a teacup. Someone making the manual checks at Mozilla fucked up and the situation was quickly admitted. I don’t know what else to wish, other than that the failure wouldn’t have happened in the first place. Sucks that it did. Now what sucks is that gorhill doesn’t want to do put it back but it is what it is, luckily it was just the Lite version.
While I like a juicy conspiracy and fuck the sytsems and all, I don’t think they were lying when they said that they’d put the addon back if gorhill just resubmitted it.
deleted by creator