3 ms·

When Firefox started to forbid unsigned extensions it was a dealbreaker and I switched to Pale Moon. I've been happier with it. I think there's a pattern where

• sp332 10y ago
  They are very protective of the Firefox trademark. They don't even put it on their own nightly builds. If you want to sideload unsigned extensions, there are first-party unbranded builds that let you do that. https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded...
• cpeterso 10y ago
  What are the unsigned extensions that you would like to use? Developers can automate the signing of the extensions, using a Mozilla service, that doesn't require the extensions be public on addons.mozilla.org.
  • acemarke 10y ago
    My personal daily workflow is heavily dependent on the old Pocket addon. That addon was deprecated a long time ago, I think even before Mozilla tried to integrate Pocket into FF. I think what I'm actually using now is a tweaked version of the addon that bumped some of the compat flag and signed it (per http://hemenkapadia.blogspot.com/2015/12/get-old-pocket-experience-on-firefox.html http://hemenkapadia.blogspot.com/2015/12/get-old-pocket-expe... ). Because of that, I'm actually way behind on the FF update curve, and holding out as long as I can. (If anyone has a pointer to an equivalent modern addon, I'd be interested.) For that matter, I'm also a die-hard TreeStyleTabs user, and I'm still not clear on whether that's going to work properly as things go forward.
    • hendersoon 10y ago
      I use a simple bookmarklet to add to pocket in Firefox. No extension needed at all! https://pastebin.mozilla.org/8969368 https://pastebin.mozilla.org/8969368
      • cpeterso 10y ago
        A limitation of bookmarklets is that it can't run on sites that use CSP to block external JavaScript. For example, I use a bookmarklet for Pinboard and I can't pin pages on github.com. Here are the Firefox and Chrome bug reports requesting that bookmarklets bypass CSP: https://bugzilla.mozilla.org/show_bug.cgi?id=866522 https://bugzilla.mozilla.org/show_bug.cgi?id=866522 https://bugs.chromium.org/p/chromium/issues/detail?id=233903 https://bugs.chromium.org/p/chromium/issues/detail?id=233903
    • cpeterso 10y ago
      You might be able to run unsigned extensions in Firefox Nightly or Developer Edition by setting the about:config pref "xpinstall.signatures.required" = false. Mozilla is testing a "TreeStyleTabs Lite" UI called Tab Center. You can install it using the Mozilla Test Pilot addon: https://testpilot.firefox.com/experiments/tab-center https://testpilot.firefox.com/experiments/tab-center
  • superkuh 10y ago
    It's not even that I was using unsigned extensions before I switched to Pale Moon. It's more that I was tweaking a good portion of the extensions I did use by popping open the xpi if required, changing a bit, then loading again. Firefox's decision completely prevented that. I wasn't going to ask Mozilla for permission (every time!) to tweak. And beyond that Pale Moon's exclusion of bloat technologies (webgl, websockets, etc, etc) and performance for >>tabs sessions just fits my use case better.
    • sp332 10y ago
      Have you considered using a Developer Edition of Firefox? That's kind of what it's aimed at supporting. https://wiki.mozilla.org/Add-ons/Extension_Signing#FAQ https://wiki.mozilla.org/Add-ons/Extension_Signing#FAQ
      • superkuh 10y ago
        Developer edition is an alpha. I don't use unstable versions of browsers for my daily driver.