Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discontinuing #122

Closed
Noitidart opened this issue Aug 25, 2018 · 60 comments
Closed

Discontinuing #122

Noitidart opened this issue Aug 25, 2018 · 60 comments

Comments

@Noitidart
Copy link
Owner

@Noitidart Noitidart commented Aug 25, 2018

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

This comment has been minimized.

Copy link

@bluenote73 bluenote73 commented Sep 2, 2018

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

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Sep 2, 2018

That's a good idea. Did it now.

@MasterOfTheTiger

This comment has been minimized.

Copy link

@MasterOfTheTiger MasterOfTheTiger commented Sep 6, 2018

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

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Sep 6, 2018

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

This comment has been minimized.

Copy link

@mzso mzso commented Oct 1, 2018

@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

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Oct 1, 2018

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

This comment has been minimized.

Copy link

@doublah doublah commented Oct 11, 2018

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

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Oct 11, 2018

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

@MasterOfTheTiger

This comment has been minimized.

Copy link

@MasterOfTheTiger MasterOfTheTiger commented Oct 11, 2018

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

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Oct 12, 2018

Thanks @MasterOfTheTiger I added MPL.

@MasterOfTheTiger

This comment has been minimized.

Copy link

@MasterOfTheTiger MasterOfTheTiger commented Oct 12, 2018

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

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Oct 12, 2018

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

@filips123

This comment has been minimized.

Copy link

@filips123 filips123 commented Oct 27, 2018

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

@QWERTYUIOPYOZO

This comment has been minimized.

Copy link
Contributor

@QWERTYUIOPYOZO QWERTYUIOPYOZO commented Oct 28, 2018

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

This comment has been minimized.

Copy link

@MasterOfTheTiger MasterOfTheTiger commented Oct 28, 2018

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

@bluenote73

This comment has been minimized.

Copy link

@bluenote73 bluenote73 commented Oct 28, 2018

Yandex Android browser supports chrome addons natively.

@filips123

This comment has been minimized.

Copy link

@filips123 filips123 commented Oct 29, 2018

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

This comment has been minimized.

Copy link

@misterhtmlcss misterhtmlcss commented Nov 8, 2018

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

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Nov 20, 2018

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

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Nov 20, 2018

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

Stanzilla added a commit to Stanzilla/refined-twitter that referenced this issue Dec 13, 2018
Chrome Store Foxified is dead (Noitidart/Chrome-Store-Foxified#122)
@andrewrembrandt

This comment has been minimized.

Copy link

@andrewrembrandt andrewrembrandt commented Jan 10, 2019

@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

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented Jan 10, 2019

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

This comment has been minimized.

Copy link

@MasterOfTheTiger MasterOfTheTiger commented Jan 10, 2019

@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.

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 17, 2019

CRXViewer worked around the CORS issue by using "domain fronting" (introduced in https://github.com/Rob--W/crxviewer/issues/58) because Firefox WONTFIXed Bug 1450649.

Just having AMO add CORS headers wont solve the issue because Firefox internally still restricts access (introduced in Bug 1415644). AMO adding CORS would probably work based on this comment: "Extensions cannot make non-CORS requests to any domain they do not have host permissions for or, as of this bug, any domain on the restricted domains list."

Oh wow no way. If this works then we can get foxified back!

@killaz47

This comment has been minimized.

Copy link

@killaz47 killaz47 commented May 19, 2019

Can you please delete the extension from AMO? It's getting bad reviews and is hurting the ratings in case you decide to bring it back to life later.

This is a good idea. Thanks very much for it. If I remove it, will @killaz47 awesome tutorial still work?

thank you Noitidart for appreciating my tutorial. especially when it's being appreciated by the chrome store foxified сreator himself. i hope, with this community support, your CTF extension is going to be fixed and working again. untill then my workaround tutorial will help.

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 19, 2019

@killaz47

This comment has been minimized.

Copy link

@killaz47 killaz47 commented May 20, 2019

:)

On Sun, May 19, 2019 at 9:01 AM killaz47 @.***> wrote: Can you please delete the extension from AMO? It's getting bad reviews and is hurting the ratings in case you decide to bring it back to life later. This is a good idea. Thanks very much for it. If I remove it, will @killaz47 https://github.com/killaz47 awesome tutorial still work? thank you Noitidart for appreciating my tutorial. especially when it's being appreciated by the chrome store foxified сreator himself. i hope, with this community support, your CTF extension is going to be fixed and working again. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#122?email_source=notifications&email_token=ABQTZCMZOPBYLLIUPAADNC3PWF2V7A5CNFSM4FRREMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVXFD6Q#issuecomment-493769210>, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQTZCIPDLYO3E6CZNEIOFLPWF2V7ANCNFSM4FRREMZQ .

the guide has been updated and is ready to be published #122 (comment)

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 20, 2019

Publish to readme!

@killaz47

This comment has been minimized.

Copy link

@killaz47 killaz47 commented May 20, 2019

Publish to readme!

Explain your meaning please?

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 20, 2019

@killaz47

This comment has been minimized.

Copy link

@killaz47 killaz47 commented May 20, 2019

Oops I meant "published". I updated the readme. :)

Excellent. Thank you.

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 20, 2019

@killaz47

This comment has been minimized.

Copy link

@killaz47 killaz47 commented May 20, 2019

I was glad to help

@SRGOM

This comment has been minimized.

Copy link

@SRGOM SRGOM commented May 20, 2019

Thank you @killaz47 this was a very well written answer!

@filips123

This comment has been minimized.

Copy link

@filips123 filips123 commented May 20, 2019

@Noitidart Will you be able to fix extension with suggestion in #122 (comment)?

@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 21, 2019

@beppe9000

This comment has been minimized.

Copy link

@beppe9000 beppe9000 commented May 25, 2019

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 added a commit that referenced this issue May 26, 2019
@Noitidart

This comment has been minimized.

Copy link
Owner Author

@Noitidart Noitidart commented May 26, 2019

Fix merged to master, thank you all! I just need to fix #120 and I can release.

@Noitidart Noitidart closed this May 26, 2019
@filips123

This comment has been minimized.

Copy link

@filips123 filips123 commented May 26, 2019

So when you fix #120, this will work again as before?

@ThePotato97

This comment has been minimized.

Copy link

@ThePotato97 ThePotato97 commented Jun 25, 2019

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

This comment has been minimized.

Copy link

@gabri25ele gabri25ele commented Jun 25, 2019

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

This comment has been minimized.

Copy link

@ThePotato97 ThePotato97 commented Jun 25, 2019

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

This comment has been minimized.

Copy link

@gabri25ele gabri25ele commented Jun 25, 2019

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

@ThePotato97

This comment has been minimized.

Copy link

@ThePotato97 ThePotato97 commented Jun 25, 2019

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

This comment has been minimized.

Copy link

@gabri25ele gabri25ele commented Jun 26, 2019

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

@glen777

This comment has been minimized.

Copy link

@glen777 glen777 commented Sep 2, 2019

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

This comment has been minimized.

Copy link

@killaz47 killaz47 commented Sep 2, 2019

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

This comment has been minimized.

Copy link

@rugk rugk commented Sep 2, 2019

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

This comment has been minimized.

Copy link

@grahamperrin grahamperrin commented Sep 4, 2019

Waterfox is the definion of legacy,

Yes and no.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.