If I got it right, the webextension port is ready or close to be since you released a chromium version of decentraleyes.
I think you should release a beta before the official release of Firefox 57. HTTPS-Everywhere just did this and the firefox and chromium API are apparently different enough to cause some issues.
I believe many followers of this github repo would be happy to help you test it.
Designs
Child items
...
Linked items
0
Link issues together to show that they're related.
Learn more.
No hurry. WebExtension is by itself a pain in the neck, moreover it won't be mandatory before Firefox 57, next November. Hence, November 2017 is the only milestone, otherwise, while we're at it, why not ask developers to update their add-ons to Nightly builds? Well, some users do, some users even score badly an add-on because it's not alpha-compatible! Hey: carpe diem! one thing at a time, please, mercy!
If the configuration of existing legacy users is to be kept and imported to any webext version, the only way to do that is with a hybrid version that embeds a transitional webext to copy existing settings into webext-accessible storage. This must be done before FF57 (because the hybrid won't be able to load at all in FF57).
I think some of the reasoning here is flawed. The FF and Chromium WebExtensions implementations are still pretty different. It is very likely that there will be bugs to fix.
What we don't know is how much time it is going to take to fix them. So the safest bet is to release the beta as soon as possible. The sooner bugs are reported, the longer @Synzvato (or anyone willing to help) will have to fix them.
Otherwise, we may possibly end up with no working decentraleyes when FF 57 comes out and it would be a shame.
[...]we may possibly end up with no working decentraleyes when FF 57 comes out and it would be a shame.
That would be no working decentraleyes on Firefox. There are alternatives to Firefox. I have in mind Waterfox if it manages to carry on legacy add-ons after Firefox 56.
Decentraleyes is a major add-on, it is for me together with a few others, not for cosmetics but for privacy and security. Should any of those add-ons not be available (sometimes because not technically feasible) that I'd move to a Firefox fork. And I won't be the only one.
@mrdokenny Thanks for the effort but if you just repacked the chrome sources I can tell you that your not the first one that tried that :) If there more I think @Synzvato would be more than happy to merge it.
The Extensions seems not to work at all (https://decentraleyes.org/test/) so I think you can just delete it again :)
@heubergen I think you are under the impression that this is my extension, but it's not. It's something I found on the mega list of WebExtension alternatives.
@mrdokenny @heubergen Thank you for looking into this fork, but it is indeed broken. It has since been removed from the list of WebExtensions equivalents, and is no longer publicly listed on AMO.
I'm actively working on porting the add-on over to Firefox 57, but doing so is more complicated than I hoped. I'm aiming for a stable release on September 1st. If the release deadline cannot be met, Mozilla will no longer longer be marking this extension as featured on AMO. It all depends on the possibilities.
The first alpha (or beta) will be made available as soon as there a working prototype. I'm happy to see that there's a lot of interest in this release, and I'll be sure to keep you all posted. Any suggestions or ideas are welcome! Please know that the development of the WebExtensions port has top priority.
The September 1st deadline is now less than one month away, but things are looking up. I'm convinced a WebExtensions port is feasible, and hope to be able to release the beta within the next two weeks.
@ronjouch This addon was already broken since version bump to 57.
No it wasn't, I was using Decentraleyes until today. (And to be totally precise, Legacy addons are still usable if you flip extensions.legacy.enabled in about:config). I was just mentioning the mailing-list announcement to share the moving WebExt-only train has arrived to the next station, in case some users are surprised by this .
Thanks, @ronjouch, @gitarra, and @darnir. Does the legacy extension pass the testing utility checks? Expect a Firefox 56 and 57 compatible WebExtensions beta within the next few days.