3 ms·

This was my experience as well and the reason I saw myself forced to use the web store. I think there was a time where it was not required, where side loading w

This was my experience as well and the reason I saw myself forced to use the web store. I think there was a time where it was not required, where side loading was ok, but then they changed it and I saw no other way to do it. IIRC there was an alternative way for enterprise users, but I never understood it. That was around 5-7 years ago and I haven't checked if there was a new alternative, easier way to do it nowadays. I'm still using my extensions but have no need to modify them. Let's see what Manifest v3 has to tell me about this. I'll probably drop Chrome then.

paulryanrogers 4y ago
Chrome allows permanent side loading, and without signing, if one enables dev mode from extensions page. Firefox requires uploading to Mozilla for signing to side load permanently or host with them. Though you can self host once signed. IME Firefox add-ons are approved almost instantly if your addon is not minified or downloading code to execute outside the package. Chrome approvals are always days.
- Hackbraten 4y ago
  > Firefox requires uploading to Mozilla for signing to side load permanently Are you sure? I’ve been sideloading extensions, signed or not, into /usr/lib/firefox/browser/extensions/ and they’ve been working fine.
  - PurpleRamen 4y ago
    When was the last time you installed a new extension that way?
    - Hackbraten 4y ago
      Last time was a few weeks ago [0]. I’m also maintaining a couple AUR packages with Firefox extensions myself. They all use the same method for persistence. I’m wondering what kind of issues people are experiencing. Haven’t heard of any myself. [0]: https://aur.archlinux.org/packages/firefox-extension-multi-account-containers https://aur.archlinux.org/packages/firefox-extension-multi-a...