-
Notifications
You must be signed in to change notification settings - Fork 69
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
Is Midori developed on Github or Gitlab? #443
Comments
It appears to me that these are two completely separate and unrelated projects. The GitLab repo is built as a electron app wrapper. This project is decidedly not. Perhaps the original registrant of midori-browser.org lost control of the domain? In which case, that should be fixed. This does raise the larger issue, that the maintainer of this project seems to be somewhat inactive. |
I stumbled across this on F-Droid, because I was looking for any new browser apps, and it's using the original logo on there. Mind you, it's a Lightning Browser fork without any mention of being one. The weird part is that this takeover has gone without explanation, making it extremely sketchy in my eyes. Even the wikipedia has been edited, but no trace of any real explanation as to why this happened. Not to mention, the website is full of things that don't mean anything, just look at it. I would really love to know what's going on, because any way I look at this, I don't like it. EDIT: I was linked this article on IRC, which raises a bunch of red flags in itself, but I guess it's something. |
Ugh. That article makes it seem somewhat official? But yeah, the no explanation thing, along with changing the entire architecture is what makes it sketch. I need a light-weight webkit based browser -- I can't actually use an electron/chromium browser in my use case -- First, the tool chains just don't exist to built it, Second, the resource constrained environment wouldn't run it. Guess it's time to fork this and try to rally devs around the new fork. |
Yeah, I don't think Electron is the right technology despite the new project readme's justification. Electron is geared towards desktop applications and has a bunch of APIs to access system resources that a regular browser either wouldn't have, or would heavily restrict. I'm also not aware of methods to isolate websites within an electron app. While I will miss Midori, I think there's enough browsers to fill its void and avoid taking up development. Have you considered Falkon (qtwebengine), Otter Browser (qtwebkit/qtwebengine), Qutebrowser (qtwebkit/qtwebengine), Epiphany (webkitgtk), Luakit (webkitgtk), surf (webkitgtk) or hell, even NetSurf (lightweight custom engine)? |
From looking at the repositories, it appears both the WebKit version and the electron version of Midori have been abandoned. However, check out Wexond. This Midori repository is actually based off of the work done here. Both Wexond and Midori appear to be identical in concept, except Wexond is actively developed. |
Thanks for the recommendation, although, as of only a month ago looks like it'll be abandonware |
I'd hate to see Midori desktop fade away. Is this github going to become the center of gravity for it having an ongoing life? |
There is still Epiphany, based on WebKit. That's what the original Midori was based on too. |
I thought Midori was originally based on or spun off of Galeon? |
I don't think so. I googled it, and Galeon was a Gecko browser. Midori was built on the WebkitGTK engine until this other group took over and decided to write it in Electron. Maybe I'm wrong. I'd never heard of Galeon before. |
Hi,
I have got a little question about Midori developing. It seems to me like there are two "Midoris". One here on GitHub and one here on GitLab. Which one is the Midori that is in Ubuntu repositories for a long time?
This repo points to https://www.midori-browser.org/ as project website and that website is pointing to the gitlab version as repository. Is this repository here on Github abadoned and Midori moved to GitLab?
The text was updated successfully, but these errors were encountered: