Disabled block_mozAddonManager, very outdated #1752
Conversation
All the linked issues are fixed since v60.0 (!) It is intentional that Addons cannot run on AMO, to avoid addons injecting malicious .xpi downloads and tricking users into installing ANYTHING. I am wondering if there are more of these extremely outdated settings...
That's not how it works. The links are to provide documentation - their state doesn't matter, and what they do could be "good" OR "bad"
Of course it is, it's one of the bugzillas linked. Do you think I just link random bugzillas and don't read them?
Did you read the user.js?
Do you really think the pref is outdated? Hint - it is NOT, it still works exactly as expected |
|
To make sure I understood this right, "blockmozaddonmanager" allows addons to access mozillas protected websites like AMO, right? There are two reasons here, pro (Mozilla is a horrible tracking company) and contra (Some random addon could manipulate links and install malicious ones). This has to be evaluated, there is no clear yes or no? I would say security is most important, and this is a basic protection mechanism. But others may say "dont install any addons apart from xyz" which could also be "the Arkenfox way". But its not simple, and for sure needs some clearer documentation instead of, again, enumerating some bugzilla reports that vary |
|
As I understand it (and I could be wrong), this does not give extensions access to the AMO, it just blocks the AMO from access certain APIs. |
bullshit - they are not in the tracking business - getting whatever analytics (engagement/usage) for their own platform(s) e.g. AMO is not fucking tracking
no it does not - read what I already said, read the user.js. it requires ANOTHER pref |
All the linked issues are fixed since v60.0 (!)
It is intentional that Addons cannot run on AMO, to avoid addons injecting malicious .xpi downloads and tricking users into installing ANYTHING.
I am wondering if there are more of these extremely outdated settings...