Re:Mozilla and Google Chrome Refuse to Support Gab’s Dissent...
by comex on Tuesday May 07, 2019 @05:04AM
(#19847671)
Neither browser allows sideloaded extensions in its standard build:
Chrome:
> As of Chrome 33, no external installs are allowed from a path to a local .crx on Windows (see Protecting Windows users from malicious extensions). As of Chrome 44, no external installs are allowed from a path to a local .crx on Mac (see Continuing to protect Chrome users from malicious extensions).
https://developer.chrome.com/apps/external_extensions
Firefox:
> What are my options if I want to install unsigned extensions in Firefox?
> The Nightly and Developer Edition versions of Firefox have a preference to disable signature enforcement.
Re:Mozilla and Google Chrome Refuse to Support Gab’s Dissent...
by madeofpalk on Tuesday May 07, 2019 @05:15AM
(#19847740)
Sure you can. You can load unpacked extensions in Chrome - I do it all the time when developing extensions.
Re:Mozilla and Google Chrome Refuse to Support Gab’s Dissent...
by starfox64_ on Tuesday May 07, 2019 @05:34AM
(#19847819)
They don't stay enabled though I think, you need to turn them back on after every restart.
Re:Mozilla and Google Chrome Refuse to Support Gab’s Dissent...
by madeofpalk on Tuesday May 07, 2019 @09:05AM
(#19848973)
That’s Safari. I have unpacked extensions loaded up in chrome all the time because I can’t figure out how to push an update to an extension I made
While troubling that they have such ability, they make their terms of use clear and do offer motivated users the ability to chose alternative plugin sources.