I’ve wanted to install an extension from outside addons.mozilla.org, but Firefox didn’t let me do it

So I’ve did a small research and looks like there are 3 ways to sideload extensions, but all of them suck

  1. Using FF Developer Edition

In the Dev Edition you can set xpinstall.signatures.required to false in about:config, but the problem is that the Dev Edition isn’t as stable as standard FF

  1. Temporarily load the extension

In about:debugging#/runtime/this-firefox you can temporarily sideload extensions, but they will be removed next time you open FF, which is annoying

  1. Modify FF code

Lastly, I found this script which modifies the FF code, but this can break things so I don’t want to use it

I’m really annoyed that Mozilla gets to decide which extensions I can install. So… what’s the best way to sideload extensions?

Edit: thanks everyone, I’m now using a FF fork (Librewolf) which lets me sideload extensions after disabling xpinstall.signatures.required

  • igorlogius@lemmy.worldEnglish
    14·
    1 year ago

    not exaclty an answer to you question … but just fyi you could also just create an AMO account (it’s free) and upload your addon for self distribution (to not have them appear on addons.mozilla.org) and then you can download and install them into stable version persistently.

    sidenote: i think instead of nightly you can also use the unbranded builds to have a stable version which allows you to use xpinstall.signatures.required. ref. https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds

    • Luna@lemdro.idOPEnglish
      3·
      1 year ago

      Oh thanks, I didn’t know about unbranded builds

      Also, regular FF stores settings and profiles in ~/.mozilla/firefox, do you know where unbranded builds of FF store them?

      Edit: nvm someone else in this thread said to open about:profiles, and the path to profile folder is there

  • redxef@feddit.de
    7·
    1 year ago

    You can place the .xpi file in a special folder. On my linux system that is in /usr/lib/firefox/browser/extensions/. Which would be the system wide folder. There are others which only affect the current user thkugh.

    The user folder is $profile_dir/extensions/. To open the profile directory you can type about:profile in you address bar and click on Open Directory besides Root Directory in the default profile section.

  • d_k_bo@feddit.de
    7·
    1 year ago

    I agree that this is annoying and feels somewhat similar to apple’s locked down ecosystem.

  • Corgana@startrek.website
    3·
    1 year ago

    Am I missing something or is it possible you’re talking about FF mobile? On PC I just drag the XPI over a FF window and the extension gets added. I just did it today, actually. No modifying needed.

  • lol@discuss.tchncs.de
    3·
    1 year ago

    I’ve been using option 3 for some time now without any problems. It’s a very small modification and I don’t see why it would break anything. Do you have any examples?

      • LinkOpensChest.wav@lemmy.one
        2·
        1 year ago

        Tbf the author writes:

        This script is not well tested, like at all. This script might break things, possibly important things. You should probably take a backup of your Firefox profile before using it. You have been warned.

        So it’s understandable that you might think it could break things.

  • Vincent@feddit.nlEnglish
    2·
    1 year ago

    If you’re talking Android, I believe the F-Droid app store (which I’d recommend anyway) packages a version of Firefox (I think called “Fennec F-Droid”?) that allows the same thing as Nightly and Beta (which I assume you mean with option 1).

    Also, Beta is very stable, just give it a shot. (Though your extensions might not be, especially on mobile.)

      • LinkOpensChest.wav@lemmy.one
        1·
        1 year ago

        Wait, so will this still require creating your own collection, or are they totally opening it up? I read the link, but I’m not sure I understand it.

        • Vincent@feddit.nl
          2·
          1 year ago

          Totally opening up, as I understand it. Which doesn’t mean that you can install every extension, because many might not be compatible. For example, Sidebery isn’t really useful on mobile, and other extensions (especially the ones still using “Manifest V2”) can’t deal well with Android unpredictably killing extension processes in the background. But every extension developer can make their extension installable by Firefox for Android users.

          • LinkOpensChest.wav@lemmy.one
            1·
            1 year ago

            People will understand that not everything is compatible, but this is still going to make it much less clunky to run add-ons that aren’t readily available now. The previous method of having to create a collection was extremely clunky and often felt like more trouble than it was worth.

  • gerbilOFdoom@beehaw.org
    2·
    1 year ago

    I’ve never had a problem side loading an entire folder into Firefox. Maybe it was an addon rather than extension though?

  • Johanno@feddit.de
    31·
    1 year ago

    Compile Firefox from scratch. Use a fork of Firefox like librewolf that allows side loading.

    (idk if librewolf allows it)