In order to keep the codebase as flexible (and the goals as focused) as possible, builds for other web browsers, such as Chrome, are not under active development at this point.
The choice for Firefox was made based on the Mozilla Foundation's organizational structure (non-profit) and its manifesto, which is very much in line with what Decentraleyes stands for as a project.
However, once Mozilla officially drops its support for XPCOM and XUL based add-ons, Decentraleyes will be ported to WebExtension (a technology designed to facilitate cross-browser compatibility). I believe that would be the right time to have a closer look at this matter.
@Synzvato I understand but IMHO "Mozilla Foundation's organizational structure (non-profit) and its manifesto" are sadly now complete bullshit. I understand we still choose at first Mozilla for its nice past. Thanks for developing decentraleyes and good luck for WebExtension port when it will be the time.
@cowlicks Since Decentraleyes leans on a couple of relatively exotic APIs, it all depends on what's possible with Mozilla's implementation of WebExtensions once it turns stable.
All I can really say at this point is that I'll try to get (or keep) essential APIs on the team's radar and will start porting the add-on to WebExtensions once I have sufficient confidence in the implementation.
There is clearly a demand for Chromium support. I know you said there's no plans for it but I think you should reconsider this request.
Actually, there are concrete plans for creating a more universal version of the add-on. Expect some details once Mozilla stabilizes their new WebExtensions API implementation.
There are plenty of open source Chrome browsers that follow Mozillas principles. Please consider porting this to chromre.
I would personally recommend Mozilla Firefox over Chromium-based browsers (including more privacy-minded solutions like SRWare Iron, for reasons such as these) to those concerned about spying. That said, I'm trying my very best to bring this concept to those who are on Chromium or Opera.
I'm actively working on it, and will get back to this issue once I have some details.
@9Morello Porting the add-on to WebExtensions is a blocking issue for its very next release. So, if all goes well, the next version will support Opera, Chromium, Chrome, and (possibly) Edge. I'm stuck waiting on an effort to bridge a small feature gap, but things are starting to look up, it seems!
@Droyk While it's theoretically possible for a WebExtensions add-on to redirect requests to local resources, this has significant security implications. That's why I'm now first aiming for additions to the current WebExtensions APIs. Until then, it's impossible for anyone to release a secure port.
Despite the various setbacks, please know that porting Decentraleyes to WebExtensions is definitely going to happen, and that it has top priority. I will be sure to keep you posted.
All I want to know is an ETA now plz don't tell me you don't have that and plz don't lie about this.
Seriously @Droyk?! It's a volunteer project. If you want to make demands on a 'product' you paying nothing for, then how about writing your own to make it on?
@Synzvato, thanks for whatever you get to do on it.
Looks like you guys got it wrong I am not making demands at all I just want to know ETA if that seems like a demand to you guys then forgive me guys I was totally wrong to ask you guys a simple ETA.
@Droyk There is no ETA. It's an old issue. And it has been closed. We will talk about an ETA when a developer will make a PR, or when the repo owner @Synzvato decides to reopen this issue. It is not the case. We are right now into the brainstorming step, not into the making and decision process.
Update: I'm still trying to find out if the issues are exploitable in Chromium. Some doubts remain, but my stance on this might change in the near future, as I haven't been able to cook up any exploits so far.
Decentraleyes is now available for Chromium-based browsers!
As a side note, the Opera-release is finished too, but is currently awaiting moderation. Apologies for the wait, but we could not release while having doubts about various security aspects. All is looking good, though. Thanks for your patience!