111–120 of 325 posts
Earlier quoted context omitted.
Don't let this hold you back. Use a mobile browser that lets you use Kagi; it's worth it.
The problem is that I like how Safari works better than any other mobile browser I have used. Wish I didn’t.
If I'm a linux user who uses firefox currently, what's the value prop for this browser? I already get privacy and extensions, is it just for testing my app on webkit?
Earlier quoted context omitted.
> A browser's whole purpose is to be online, after all. Not its whole purpose. I use browsers offline fairly often. Offline installers (for any piece of software) are important to me because they allow me to keep a backup of the installer and won't restrict me when I don't have internet access. Keeping a backup is important because it lets me install older versions of the software when needed.
I respect your choice, but browsers are the one piece of software that you never, ever want to run an outdated version of. Websites really just don't stop working for new versions of browsers; browser/standards compatibility essentially only improves with time. The only thing you're getting with an old version is all of the security issues.
Has Orion gotten significantly more stable in the last year? The last time I tried it, on iOS, it crashed a lot.
Earlier quoted context omitted.
Just curious, but is this really a big deal? As a customer, you already trust Kagi enough to feed them your entire search history, so I guess you don't think they're bad actors. Thus, why you find problematic the (momentary?) "unopeness" of the browser? I'd gladly try it (I'm on Arch), even just out of curiosity (unlikely to make it my main, though). Jeez, downvoted for asking about context? People, calm down.
Requiring it to be open source is not just about trusting the publisher. There are a bunch of other possible reasons, including wanting to support open source as a counterbalance to proprietary software. For me, it's a big deal (although not a dealbreaker) for that reason. If I have the option of two different pieces of software, one being open source and the other proprietary, I'll choose the open source one every t…
This is a healthy thing to happen to the Linux browser ecosystem imho. We talk a lot about browser diversity, but on Linux and Windows, it is a lie. You have firefox (gecko) and fifty flavors of chromium. Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser, which I'll admit while is a noble effort, lags a bit in the stability and power-user features department. Big reason…
> The sticking point like always will be media playback (read: DRM/widevine). Probably true in general. But for me, that's not a sticking point at all. I don't care if a browser supports media playback or not. What I do care about is the ability to enable/disable embedded code execution (JS, at the very least) at a fairly granular level. Does Orion allow for that?
This is a healthy thing to happen to the Linux browser ecosystem imho. We talk a lot about browser diversity, but on Linux and Windows, it is a lie. You have firefox (gecko) and fifty flavors of chromium. Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser, which I'll admit while is a noble effort, lags a bit in the stability and power-user features department. Big reason…
> Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser Don't forget about https://falkon.org . It's a browser I enjoy using. WebExtension support will be big if it lands in Orion though. EDIT: apparently Orion is not open source. Not particularly interested in a closed source browser, TBH. In 2022 they said they plan to open source "when there is merit"[1], whatever that me…
This is a healthy thing to happen to the Linux browser ecosystem imho. We talk a lot about browser diversity, but on Linux and Windows, it is a lie. You have firefox (gecko) and fifty flavors of chromium. Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser, which I'll admit while is a noble effort, lags a bit in the stability and power-user features department. Big reason…
> The sticking point like always will be media playback (read: DRM/widevine). That is the graveyard where Linux browsers go to die. If Kagi can legally and technically solve the widevine integration on a non-standard Linux webkit build, they win. If not, it will be a secondary browser for documentation reading only. I'm hopeful that some day Linux will have enough users where the media companies can't ignore them. Ho…
This is a healthy thing to happen to the Linux browser ecosystem imho. We talk a lot about browser diversity, but on Linux and Windows, it is a lie. You have firefox (gecko) and fifty flavors of chromium. Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser, which I'll admit while is a noble effort, lags a bit in the stability and power-user features department. Big reason…
> The sticking point like always will be media playback (read: DRM/widevine). That is the graveyard where Linux browsers go to die. If Kagi can legally and technically solve the widevine integration on a non-standard Linux webkit build, they win. If not, it will be a secondary browser for documentation reading only. I'm hopeful that some day Linux will have enough users where the media companies can't ignore them. Ho…