4 ms·

You can argue for or against `fixamo` as a command, but Mozilla's position seems to be that even documenting the ability to turn off restrictedDomains anywhere

You can argue for or against `fixamo` as a command, but Mozilla's position seems to be that even documenting the ability to turn off restrictedDomains anywhere is not allowed. Among other things they're asking the author to censor the command from his personal dotfile. That's not justifiable and makes me really disappointed in Mozilla.

detaro 7y ago
The "personal dotfile" that's lives in the same repo as the extension and is recommended as an example in its documentation, and only documents these commends as "Add helper commands that Mozillians think make Firefox irredeemably insecure". If you want to signal to a reviewer you're not taking them seriously, that's the kind of thing to do when they ask you to remove code.
- cmcaine 7y ago
  In our defence 1. that's a perfectly sensible comment to suggest that you should probably look it up on your own if you care about security. 2. The command did document exactly what it did in the same manner (or more detail) as the blogs we got it from. 3. We invited Mozilla to provide text for us to comment it with and they didn't give us any. Edit: And as bovine3dom says, this was done in response to an informal request by someone reasonably friendly to the project.
- bovine3dom 7y ago
  `fixamo` was first removed after an informal request via informal channels from someone on the Firefox security team. The comment wasn't intended as a jab at a reviewer who didn't exist at that time; I was just tickling myself as is my wont. I'm sorry if it offended anyone. I'm generally really appreciative of the work reviewers do.
  - detaro 7y ago
    Ah, I had missed that aspect. That paints it in a different light.