2. Even when "enabled" in the add-on manager, the add-on was completely inert unless a user also manually dove into about:config and specifically enabled a flag related to the add-on. Without taking that deliberate action, it didn't do anything but watch that flag. No headers, no word inversions, etc.
If you'd like to verify my claims, the source lives at https://github.com/mozilla/addon-wr, and initialization is controlled by addon/bootstrap.js.
This doesn't excuse our actions, but I hope it adds some context.
1. The study is not "still active and ongoing." It was pulled yesterday after the backlash, though that may take up to 24 hours to propagate: https://gizmodo.com/after-blowback-firefox-will-move-mr-robo...
2. Even when "enabled" in the add-on manager, the add-on was completely inert unless a user also manually dove into about:config and specifically enabled a flag related to the add-on. Without taking that deliberate action, it didn't do anything but watch that flag. No headers, no word inversions, etc.
If you'd like to verify my claims, the source lives at https://github.com/mozilla/addon-wr, and initialization is controlled by addon/bootstrap.js.
This doesn't excuse our actions, but I hope it adds some context.