Discontinuing

[Noitidart]

Hi all,

Excuse my ignoring of all the issues. Mozilla keeps changing things. The latest is some issues with addons.mozilla.org fetch requests.

The effort I put into extension development isn't working out. I have to do side jobs so I can fund the time I spend developing. I wish I could make extension development my primary contribution, however it can never get to this point, extensions just don't work like that. I tried, I put up a contribute sign and I want to thank everyone that contributed, I have got $318 USD in the past year. I made an effort to thank everyone that contributed, and will be going through again to make sure I didn't miss sending thank you notes.

I have moved into mobile apps which pays for itself.

If anyone knows of anyone that can invest in any kind of development (browser, mobile, desktop), I would love to chat.

I have not yet removed the extension because it is still working in older versions of the browser, including ESR release channel.

[bluenote73]

At least go and update the description on the addon page so you stop wasting people's time.

[Noitidart]

That's a good idea. Did it now.

[MasterOfTheTiger]

I would like to know what it would take to help out in maintaining it.

[Noitidart]

Thanks @MasterOfTheTiger - You would need to move things to server side to get around Mozilla blocking the fetch on AMO endpoints to do the signing. You can also try to petition the AMO API devs.

The blocking of fetch on AMO prevents me from automatically extracting user token needed for the signing process. You'll need to teach users how to extract that. I don't think it can be done automatically anymore even with content scripts. One option is to use a single account to sign everything, however AMO reviewers rejected that idea in the past.

[mzso]

@Noitidart commented on 2018. aug. 25. 09:29 CEST:

I have moved into mobile apps which pays for itself.

Hi!

Out of curiosity, what kind of mobil apps are you developing?

[Noitidart]

Thanks for asking @mzso - I use React Native so I do ios and android. The type of the app varies. But it's all stuff that I use personally. Just like the extensions I made were extensions I would personally need/use.

[doublah]

Any chance of a clear LICENSE file in the repo?
The package.json file lists the license as ISC, yet the page in some other files and on AMO lists the license as MPL 2.0. A clear license means a fork would be more likely, thanks.

[Noitidart]

I never understood licenses. Whatever promotes most likely fork I'll throw it on there. Any advice?

[MasterOfTheTiger]

The MIT (or ISC since its already there) is very permissive. The MPL is good if you want others to have to also release the source code (copyleft).

I am not a lawyer, this is not legal advice, etc.

[Noitidart]

Thanks @MasterOfTheTiger I added MPL.

[MasterOfTheTiger]

I am going to look through the code and see how well I could actually fork the project.

[Noitidart]

The next version would have to be very different. Everything has to be done server side due to AMO changes.

[filips123]

@Noitidart @MasterOfTheTiger @doublah
Are there some alternatives to this addon? Can someone fork and continue developing it?

[PatrickGuthridge]

After my school exams, I will try and find some time to make an extension for this purpose. It will use my home server to download and sign extensions for users. Only problem is that my network connection is only 50mbps down and 10mbps up.

[MasterOfTheTiger]

I want to fork it, but I need time to both figure out if I can do it and if I have time.

[bluenote73]

Yandex Android browser supports chrome addons natively.

[filips123]

If some of you will fork, please collaborate with each other, because it will not be good if there will be 100 unofficial forks.

[misterhtmlcss]

No idea why we are talking fork when the author is telling you he can't devote his life to it. He's not (IMO) telling us he doesn't value the extension any longer, he's saying he can't devote so much time to it. I think the way to respect him if you want to keep it going is to work with him rather than Fork and be like 'see ya dude'. @Noitidart am I wrong? I think you'd like to keep it going, but it can't be the @Noitidart show any longer correct?

[Noitidart]

Sincerest thanks @misterhtmlcss - major apologies for missing your message. I would absolutely love nothing more then to devote my time to this extension and my other extensions, bringing them back to life better then before(namely: NativeShot & MailtoWebmails), it's just financially not feasible. :(

Sincerest thanks @misterhtmlcss for your great comment!

[Noitidart]

I would definitely love to see a fork, I will update the readme to point to the one we decide on.

[andrewrembrandt]

@Noitidart / @MasterOfTheTiger - if it helps, I'll fund a development server (and hopefully have time to set it up - at least in a month) - let me know? (by email, or on here)

[Noitidart]

That would be awesome, server costs can get high though. I heard AWS EC2 node apps can get up to 40 bucks a month.

[MasterOfTheTiger]

@Noitidart @andrewrembrandt I have not had a chance to dig through the code yet, but that sounds good, but as @Noitidart said, pricing can get high. So if we set up a website and set up donations it might be able to make ends meet. I will look into the code later this week.

[ImprovedTube]

We would host too. By the way guys, let's bring legacy extensions back to life https://archive.org/details/addons.mozilla.org_legacy_201810

…

On Thu, Jan 10, 2019 at 9:34 PM MasterOfTheTiger ***@***.***> wrote: @Noitidart <https://github.com/Noitidart> @andrewrembrandt <https://github.com/andrewrembrandt> I have not had a chance to dig through the code yet, but that sounds good, but as @Noitidart <https://github.com/Noitidart> said, pricing can get high. So if we set up a website and set up donations it might be able to make ends meet. I will look into the code later this week. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#122 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AX3PJeJ6RxOQs9CGBKxmkJ2sPK2ol7wtks5vB6PtgaJpZM4WMSMz> .

[Noitidart]

@filip yes I'm going to try. It seems I have to add cookie support.

…

On Mon, May 20, 2019 at 10:45 AM Filip Š ***@***.***> wrote: @Noitidart <https://github.com/Noitidart> Will you be able to fix extension with suggestion in mozilla/addons-server#122 (comment) <#122 (comment)> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#122?email_source=notifications&email_token=ABQTZCI5PCZDXDBUQOYN66TPWLPSPA5CNFSM4FRREMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVZSH3A#issuecomment-494085100>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQTZCJNQBGDA6DI52EBA6DPWLPSPANCNFSM4FRREMZQ> .

[beppe9000]

Is the whole raw process of producing an xpi documented somewhere or I have to check the actual code?
I was thinking about alternate ways of install.

[Noitidart]

Fix merged to master, thank you all! I just need to fix mozilla/addons-server#120 and I can release.

[filips123]

So when you fix mozilla/addons-server#120, this will work again as before?

[ThePotato97]

Editing "extensions.webextensions.restrictedDomains" in about:config worked a bit for me Firefox Nightly version 69.0a1 https://streamable.com/unocn sometimes gets stuck on "Uploading for review"

[gabri25ele]

Editing "extensions.webextensions.restrictedDomains" in about:config worked a bit for me Firefox Nightly version 69.0a1 https://streamable.com/unocn sometimes gets stuck on "Uploading for review"

my value is "accounts-static.cdn.mozilla.net,accounts.firefox.com,addons.cdn.mozilla.net,addons.mozilla.org,api.accounts.firefox.com,content.cdn.mozilla.net,discovery.addons.mozilla.org,install.mozilla.org,oauth.accounts.firefox.com,profile.accounts.firefox.com,support.mozilla.org,sync.services.mozilla.com"
what is yours?

[ThePotato97]

Editing "extensions.webextensions.restrictedDomains" in about:config worked a bit for me Firefox Nightly version 69.0a1 https://streamable.com/unocn sometimes gets stuck on "Uploading for review"

my value is "accounts-static.cdn.mozilla.net,accounts.firefox.com,addons.cdn.mozilla.net,addons.mozilla.org,api.accounts.firefox.com,content.cdn.mozilla.net,discovery.addons.mozilla.org,install.mozilla.org,oauth.accounts.firefox.com,profile.accounts.firefox.com,support.mozilla.org,sync.services.mozilla.com"
what is yours?

I deleted it all but removing just ",addons.mozilla.org" might work

[gabri25ele]

Firefox 69.0a1: I deleted all, but not work anymore for example with this link
https://chrome.google.com/webstore/detail/s3translator/debnnjfbneojbmioajinefnflopdohjk

[ThePotato97]

Firefox 69.0a1: I deleted all, but not work anymore for example with this link
https://chrome.google.com/webstore/detail/s3translator/debnnjfbneojbmioajinefnflopdohjk

try downloading the crx file and reinstalling the addon https://streamable.com/tgsoe

[gabri25ele]

nothing 😥
did you try the linked extension? (https://chrome.google.com/webstore/detail/s3translator/debnnjfbneojbmioajinefnflopdohjk)
in your Firefox, it works?

[glen777]

It is easy to get around most of Mozilla's crazy restrictions if you switch to the forked successor of firefox: Waterfox. Addons do not need to be signed in Waterfox, and you have a lot more freedom in what you want to do. Even legacy addons can sometimes work there, especially if you turn off eletrolysis. I don't know why anyone still uses the min branch of firefox when Waterfox offers so much more. It's a bit faster, too.

[killaz47]

Firefox developer edition and nightly build(with a slight tweaking of about:config parameters, changing which on the public stable Firefox release has no effect) are able to work without add-on signing, so as with legacy support.

[rugk]

Waterfox is the definion of legacy, which you actually support by saying:

Even legacy addons can sometimes work there, especially if you turn off eletrolysis

Well... it's just that Electrolysis (e10s) is the future and makes Firefox much faster than without it (and more secure, due to isolation in seperate processes). See https://wiki.mozilla.org/Electrolysis

Also disabling add-on signing disables a security feature.

Anyway, this is off-topic anyway.

[grahamperrin]

Waterfox is the definion of legacy,

Yes and no.

Waterfox Classic 2019.12, Waterfox Current 2019.10 (2019.12 in the pipeline.

[cherryswiftie13]

i can't believe this extension has been discontinued! i mean, @Noitidart i fully understand the situation. i'm just sad that this is the only extension out there that allows users to install chrome extensions on firefox

[e-t-l]

I would definitely love to see a fork, I will update the readme to point to the one we decide on.

Are there any actual forks that are still being maintained? All the ones I've looked at are behind this repo in terms of commits.

[asegerno]

Installing Chrome extensions on Firefox, self-made (killaz47) tested workaround:

1. install (extract) firefox 56.0.1 portable from https://sourceforge.net/projects/portableapps/files/Mozilla%20Firefox%2C%20Portable%20Ed./

                   an example of an conversion of a chrome extension
   

2. copy an url to your derired chrome extension https://chrome.google.com/webstore/detail/web-videos-saver/odecbmmehabeloobkgokmfgldaegiflc
3. close your primary/installed, latest firefox, and lauch the firefox portable 56.0.1 edition from the previously extracted folder
4. create an account on https://addons.mozilla.org/en-US/firefox/ and log in (or log in instantly if you have it)
5. install https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/ itself
6. then use “chrome store foxified” it as it meant to be&&&1&&&,by:
   a) (in most cases)going to your (previously copied) url of a desired chrome extension https://chrome.google.com/webstore/detail/web-videos-saver/odecbmmehabeloobkgokmfgldaegiflc and by clicking on the "add to firefox, available on chrome".
   b) Installing it from (chrome extension file format) .crx file, which you can get by:
   b.1) using “get crx” chrome extension https://chrome.google.com/webstore/detail/get-crx/dijpllakibenlejkbajahncialkbdkjc
   b.2) (useful if you have your extension installed, thus obtaining ext. ID (developer mode must be enabled in the extensions menu), but for some some reasons can’t get its chrome store url page) using https://chrome-extension-downloader.com/website
   b.3) (useful if you want to use older version of chrome extension or its not existing on chrome store anymore) open your extension menu via settings or by url chrome://extensions/, Enable Developer Mode by clicking the toggle switch next to “Developer mode”, click on your extension, look up for its ID, get the same-named folder from “c:\Users[username]\AppData&&&2&&&\Local\Google\Chrome\User Data\Default\Extensions\” to some temporary folder, then, in chrome extension menu, click on “pack extension” button to pack your copied folder with the extension internal content to .crx file.

7.1. (if direct usage, by using chrome extension url,was chosen)“chrome store foxified” tab will open, for the first time you'll have to read an accept (with CATCHPA) an Mozilla AMO agreement 7.2. (if installing from .crx file was chosen) click on the “chrome store foxified” icon on top right of Mozilla toolbar, )“chrome store foxified” tab will open, click on the “No file selected - click here to browse” string below the “my computer” heading, and choose your previously downloaded .crx file, click “add to firefox”, file was added for conversion, for the first time you'll have to read an accept (with CATCHPA) an Mozilla AMO agreement, after accepting, the conversion should begin(messaging “uploading for review…-waiting for review X sec-downloading signed extension”)

1. After the conversion, the (desired chrome) extension “add” button will pop-up on the top-right corner of the Firefox (in other words, it would be installed as a usual firefox extension).
2. Go to about:debugging in the url address bar, then check “enable add-on debugging”.
3. Scroll down until you see your (chrome converted) extension id. An extension from this example, web videos saver, has “Extension ID odecbmmehabeloobkgokmfgldaegiflc@chrome-store-foxified-887013873”.
4. Close firefox portable, then go to [firefox portable folder]\Data\profile\extensions\ you’ll see the extension .xpi file with named as extension ID, so by this example its “odecbmmehabeloobkgokmfgldaegiflc@chrome-store-foxified-887013873.xpi”.
5. You can either
   12.1. Copy this .xpi file to (hidden folders option must be enabled in windows explorer https://support.microsoft.com/en-us/help/14201/windows-show-hidden-files) c:\Users[user name folder]\AppData&&&3&&&\Roaming\Mozilla\Firefox\Profiles[Mozilla profile name folder]&&&4&&&\extensions
   12.2. . install it manually in your primary/installed, latest firefox from an previously extracted .xpi file (copied to, for example, your desktop) then by following these steps:
   • Access the Add-ons interface. Go to Settings (☰) > Add-ons. This page will display any installed extensions. From here you can update, remove, or search for new extensions and add-ons. This page can also be accessed by pressing Ctrl+Shift+A or by typing “about:addons” into the address bar.
   • Access the add-ons interface controls. From the add-ons interface, press Settings (gear icon) next to the add-on search bar. This will open a menu of add-on specific controls.
   • Select “Install Add-on from File…” from the menu. This will bring up a file explorer window.
   • Verify installation. Press “Install” in the notification and restart Firefox if necessary.
6. Done, Chrome extension has been installed on Firefox successfully.

_references (marked as &&&x number&&&, due to limited github text editing)

1. several chrome store foxified guides are available https://www.google.com/search?client=firefox-b-d&q=how+to+install+chrome+extensions+on+firefox 2. hidden folders option must be enabled in windows explorer https://support.microsoft.com/en-us/help/14201/windows-show-hidden-files 3. same, hidden folders option must be enabled in windows explorer https://support.microsoft.com/en-us/help/14201/windows-show-hidden-files 4. Mozilla profile name and its folder path can be discovered by following these steps: • Step 1: Launch Firefox. Press Alt key on the keyboard to see Firefox menus. • Step 2: Click the Help menu and then click Troubleshooting Information option. This action will open Troubleshooting Information page. • Step 3: Here, under Application Basics, look for Profile Folder. Next to it, there is Open Folder button. Click Open Folder button to open your Firefox profile folder._

Can you write a command execution auto file?
The plugin web is no longer available

[glen777]

That's great. Thanks for your work and all the info. (Though I've mostly given up on firefox, and moved to palemoon and chromium)

[tastyratz]

From what I can tell trying things today, sadly, the instructions do not work anymore.

Chrome 44 and above require signing to install an extension. You can load it temporarily under about:debugging , but, it doesn't actually work.
I tried using 43 and it says the extension is not compatible. I then downloaded 56.0.1 developer edition and it loaded! When I go to the web page for the addon I wanted to use (in this case, cluster tab management) and click add to firefox I see:

Server issues with Chrome Web Store, failed to fetch extension data. Status Text: "No Content". Status Code: "204". Reason: "undefined".

I decided to try taking a stab at running a local copy of foxify https://github.com/bnpoirier/foxify since this always worked best for me when the site was live (it's now down) but, I am out of my expertise there and failed miserably. @bnpoirier hasn't been active on git in over a year either from what I can see :-(

Oh, I very much wish these things worked. Sadly, I have had no such luck. I wanted to report back so someone else doesn't spend a night to reach the same fruitless conclusion (or share to me the cleraly missing winning tip).

[asegerno]

From what I can tell trying things today, sadly, the instructions do not work anymore.

Chrome 44 and above require signing to install an extension. You can load it temporarily under about:debugging , but, it doesn't actually work. I tried using 43 and it says the extension is not compatible. I then downloaded 56.0.1 developer edition and it loaded! When I go to the web page for the addon I wanted to use (in this case, cluster tab management) and click add to firefox I see:

Server issues with Chrome Web Store, failed to fetch extension data. Status Text: "No Content". Status Code: "204". Reason: "undefined".

I decided to try taking a stab at running a local copy of foxify https://github.com/bnpoirier/foxify since this always worked best for me when the site was live (it's now down) but, I am out of my expertise there and failed miserably. @bnpoirier hasn't been active on git in over a year either from what I can see :-(

Oh, I very much wish these things worked. Sadly, I have had no such luck. I wanted to report back so someone else doesn't spend a night to reach the same fruitless conclusion (or share to me the cleraly missing winning tip).

Short sentence, looking for a new project partner, Good luck for you

[bnpoirier]

From what I can tell trying things today, sadly, the instructions do not work anymore.

Chrome 44 and above require signing to install an extension. You can load it temporarily under about:debugging , but, it doesn't actually work. I tried using 43 and it says the extension is not compatible. I then downloaded 56.0.1 developer edition and it loaded! When I go to the web page for the addon I wanted to use (in this case, cluster tab management) and click add to firefox I see:

Server issues with Chrome Web Store, failed to fetch extension data. Status Text: "No Content". Status Code: "204". Reason: "undefined".

I decided to try taking a stab at running a local copy of foxify https://github.com/bnpoirier/foxify since this always worked best for me when the site was live (it's now down) but, I am out of my expertise there and failed miserably. @bnpoirier hasn't been active on git in over a year either from what I can see :-(

Oh, I very much wish these things worked. Sadly, I have had no such luck. I wanted to report back so someone else doesn't spend a night to reach the same fruitless conclusion (or share to me the cleraly missing winning tip).

Hello @tastyratz and @asegerno, I received an email today from both of your mentions and I was surprised because I thought nobody was using my project and finally discovered that you and some Reddit users have used it in the past. I did Foxify when I was student and stopped maintaining it a few months after it's release when Mozilla decided to deny installation of non-signed extension. My website went useless as it's now hard to install a non-signed extension while it was just a matter of click before.

Maybe I should update the project, but I don't have much time these days to update it to be honest. I'll see what can I do.

[tastyratz]

@bnpoirier Glad to hear you're around and doing well. A lot of extensions are cross developed these days (except usually just the 1 critical one it seems). Your work on this is appreciated and I definitely found it invaluable in the past. I've definitely used it several times.

[e-t-l]

I created a Mozilla developer account (it's not too hard all things considered) so I can sign FF add-ons. By signing them myself, I'm still able to use and install foxified add-ons. It's an additional step, sure, but the general process still works.

[asegerno]

Hello @tastyratz and @asegerno, I received an email today from both of your mentions and I was surprised because I thought nobody was using my project and finally discovered that you and some Reddit users have used it in the past. I did Foxify when I was student and stopped maintaining it a few months after it's release when Mozilla decided to deny installation of non-signed extension. My website went useless as it's now hard to install a non-signed extension while it was just a matter of click before.

Maybe I should update the project, but I don't have much time these days to update it to be honest. I'll see what can I do.

If you can't make a Firefox by application, solution you can make an "Open Source Firefox" by application like Waterfox and Pale Moon

[Aleksandra0056]

So you are saying, that the Chrome Store Foxified is no longer available due to discontinuation of XPCOM?

[Aleksandra0056]

Well if I'm right, then there should be an alternative solution, like helper scripts that allow XPCOM extensions to work in Firefox v57+. In example: userChromeJS in https://github.com/xiaoxiaoflood/firefox-scripts but it is a little bit different to implement this through userChromeJS, because Firefox internal component for loading XPCOM extensions is different than userChromeJS.

Just let me know if I'm right, or if I didn't understood.