Another vote for Gnome, it's Linux, we are all running QT apps in Gnome and GTK apps in Plasma... stick with Webkit.
Orion for Linux
Another vote for Webkit!! This thread is super exciting. I will gladly become a paid supporter once available on GNU/Linux!
I vote for webkit. I agree that there's enough crhromium browsers
- Edited
one vote more for webkit, free me of the chromium reign!
can't wait to be able to use the same browser in iOS, mac os and linux.
PS. yeah, just trying to stay away from windows as far as possible
gp I think Flatpak is the way to go. At the very least Flatpak should be the focus.
A containerized application means the developers of Orion for Linux can include all required dependencies. They don't need to concern themselves with different packaging formats like .deb or .rpm.
As Flathub is planning on including payment for applications for applications distributed through them Orion unlocks a potential new source of revenue. Payments can be optional to keep the app free for users who are unsure.
The installation is basically a one-click affair. Users can install Flatpaks through GNOME Software or Discover on KDE Plasma.
GNOME Web/Epiphany is already distributed via Flathub and uses WebKit so there should no issues with WebKit itself.
Sorry to report that the contractor team who was supposed to work on this bailed out. We are back to putting this on hold.
- Edited
I am not a developer, so please excuse my ignorance, but would a Flatpak or AppImage be a viable way to move forward since they are supported on almost all distros and DE? If not, I would like to put a vote in for the Gnome DE if this project gets up and running again.
@Vlad
What about making a kickstarter/founding for Linux/Windows/Android Orion?
I gotta say, me and a lot of other members would contribute. Idk, you guys could decide which platform would be better to launch first among the three options and then start a founding to gather enough resources to make it happen.
I mean, I gotta say, personally, I haven't bought Orion+ cause it's just for Apple, I'm mostly Windows/Linux/Android user. With a founding project, I believe we can make it happen.
TheLastEnvoy Not a bad idea, but raising money is just one part of equation, the other is finding people who can build a browser on Linux. If anyone know any of this caliber please send them our way so that we can assess how much money we will need to raise in the first place.
I know this isn't being worked on now, but I figured I'd chime in.
I'm personally using KDE as my DE, so I'd vote for anything that lets me use the browser in KDE.
If this does ever get picked up again, I hope you're able to stick with GTK and webkit.
Hello everyone, I think that regarding this topic @Vlad should clarify what is the main goal of kagi, if it is to bring webkit in each Os we will to wait a long time if instead the goal is to make available a zero telemetry and light and then consider using geko for other Os?
The last one seems strange given the huge work they are doing to bring the extensions to webkit
Good luck, and hope this initiative is picked back up.
Worth noting that using WebKit on Linux doesn't limit you to GTK/Gnome, as WebKit for Embedded (WPE) can output a texture directly. I built a proof-of-concept browser using direct GL rendering with Sway on Wayland using WPE, (see also Cog).
I've done some experimental work (and so has Igalia for Epiphany/Gnome Web) on implementing the Web Extensions standard (Mozilla), with the goal of supporting at least BitWarden and uBlock Origin. Performance is great and easy to have multiprocess renderering / suspended tabs etc.
tokyovigilante you should reach out to hello@kagi.com if you want a job doing this
- Edited
Do you think creating a Kickstarter with different buckets (Android / Windows / Linux) could still help build a plan?
I completely understand your point - you still need to find a good team that can pull this off in a reasonable timeframe. But I'm assuming it's not the same to go head hunting with a budget of 100k than, say, 1M
The nice thing about the fundraising approach is that, unlike the Orion+ subscription approach, people aren't just giving money away blindly. They would know they will only be spending that money if the browser is actually delivered for the platform they use.
Also, I'm thinking maybe you could allow people to aim their contributions at more than one platform. Meaning, one can contribute to, say, Android OR Linux, and their money can be used for either of them - whatever target is reached first (and a suitable team is found).
I say this because, as others have said, it's a bit of a chicken and egg situation. I'm paying for Kagi (Search) and I have tried (and liked) Orion on my work-issued MacBook. However, my personal devices are a Windows PC and an Android phone... so that's where my Orion journey ended. I can't keep syncing my Firefox bookmarks, history and extensions to Orion, so I just ended up dropping Orion altogether and coming back to Firefox on my Mac as well.
On one hand, I want to pay in order to support an Android version especially. But on the other, I feel like by subscribing to Orion+ I'm not really doing that. At best, maybe I'm contributing to the Linux version that's in the backlog, which I'm not interested in. I also have no reference of the actual impact of my contributions, because there are no specific goals or pricetags attached to them.
I feel like having a specific goal of, say, 300k to develop an Android version, 200k to develop a Linux version, etc., and allowing us to contribute and see how close each target is might help steer people to contribute. And who knows... maybe word will get out and you'll get more support than expected?
I know it's probably a big challenge in itself to simply estimate how much each development would cost in order to set the targets. But it might just be a worthwhile exercise to do.
Anyway, just a thought!
Vlad
Thanks for the offer, I have some other projects on currently so this would be somewhere between a hobby and a side project for me.
For now I'd settle for a steer on whether you're preferring a GTK-centric approach (ie using WebKitGTK) or a more standalone approach with WPE. I note the latter approach is more or less how Vivaldi works (rendering its interface in HTML inside a Chromium iframe) but I'm warming to the GTK(4) approach given how nicely Swift is looking like integrating with libadwaita, and hopefully then enabling maximal code-sharing with at least the macOS version of Orion.