Hacker News new | ask | show | jobs
by infecto 939 days ago
I am hopeful for its development but it’s not a daily driver for me. Too many bugs, not a large enough team to support it. When I have looked at the support forum the developer is sometimes a little hostile about bugs/issues, enough so that I don’t care to report my own issues. This is a subjective statement your experience may differ.
3 comments

Yeah. What a waste of time for Kagi. Isn’t search hard enough? Wouldn’t that dev time be better spent on their main product?
I agree. I love Kagi search but this seems to have no unique features over other browsers. You are better off using your otherwise favourite browser and changing the default search engine as far as I can tell.
It has many unique features over other browsers. To begin with, it is zero telemetry by default. It is also the fastest browser on Mac as measured by Speedometer. And it supports both Chrome and Firefox extensions, in a WebKit based browser. This should be a good start.
Zero telemetry and fastest aren't unique features (assuming that fastest is not notably true, since every browser seems to be the fastest in some benchmark or another). Supporting both Chrome and Firefox extensions may be, but that seems like a very small niche?
Perhaps, but it is the only browser in the known universe that runs Chrome and Firefox web extensions on iOS, which is on billion devices.

Zero telemetry may not be a unique feature to you, but if you care about having a privacy respecting browser it certainly is. If a browser has telemetry, which almost every other browser has, it is not privacy respecting by definition.

Ok, now that is a unique feature! Bringing that large library of extensions to a pretty locked down platform is definitely a selling point.

> Zero telemetry may not be a unique feature to you

Unique does not mean important. It means hard to find elsewhere. There are lots of browsers that have zero telemetry. Adding another one doesn't stand out. It can be an important feature of a browser but it alone won't bring many people to a new browser when they can get it elsewhere in a more established product.

Just to add, the main complaint I have had with it is the memory leaks/bloat. For example, I sometimes listen to music via youtube while working and after a couple hours the video player interface will become unresponsive, you click pause and it takes 5 seconds for the video to pause. This problem has been around for over a year, I remember seeing some similar posts on the support forum but it was kind of dismissive. This kind of bug is a deal breaker for me.
This is also a problem with Safari. Leaving websites with a ton of dynamic content leads to the whole browser becoming unresponsive.
Never experienced it with Youtube in Safari but it happens 100% of the time in Orion.
For me the highest stopper is that it does not really work with Google Meet and it is not clear if it is a Webkit bug or not. Apart from that, I could probably use it as a daily driver.
> that it does not really work with Google Meet

It does sound like a feature, not a bug though...

My "favourite" feature about Meet is that it takes me through all these self-satisfied feature announcement popups to explain to me how all these different things work. every. single. call.

I use meet as seldom as possible (basically just when a client, partner org etc sets up a call) but it still adds up to at least 2 or 3 a week at minimum. I wasn't interested in those feature popups the first time I'm definitely not interested now after you've been showing them to me 2 or 3 times a week for the last year or so. There doesn't seem any way to make it stop though.

Careful, someone at Google reading this will green light a new version. Google has gone from talk to hangouts to meet and gotten even more proprietary with each iteration. I’m sure there is someone itching to create yet a new name/version that would have new draconian DRM. Heck, they might even try and bring something like ActiveX back if they knew it would make a users experience worse.
This. Meet works better with Chrome, so I used to have chrome for Meet only, and Firefox for everything else.
I have chromium on my computer for meet and microsoft teams. The rest I do with firefox.
I’ve so consistently had issues with Google products on Firefox, that I can’t help but feel it’s intentional.

At this point I keep a chromium based browser around as my google apps portal, and nothing else.

Change your user agent so it looks like chrome, life is better then.
It has become better in the last year or so. I used to have the same setup but currently Meet on FF works without issues for me.
Yes, it's better, but you cannot share a browser tab, only a window or the full desktop.

Edit to add that the suggestion of using Orion for everyday browsing and FF or Chrome/EDge for Google Meet is totally reasonable, but somehow I find quite a lot of friction doing that.