News for hackers. Stuff that matters.
Re:The next Google by sillysaurusx on Tuesday April 05, 2022 @01:56PM (#30922477)
A paid search engine? Bold. I'd pay if it could do anything close to what the old google code search could do. I miss it every day.
Re:The next Google by fallat on Tuesday April 05, 2022 @02:24PM (#30922867)
It's actually so good I plan to pay when they start charging.
Re:The next Google by spiderice on Tuesday April 05, 2022 @04:18PM (#30924443)
It's really good in some ways, and very lacking (for me) in others. The search is fine. Good enough that I would switch. However, if I was out and about and quickly needed directions to Walmart, my normal flow with Google is

Pull out phone -> Safari -> type "Walmart" -> click on the map -> Maps app opens and starts guiding me

When I switched to Kagi, the flow went like

Pull out phone -> Safari -> type "Walmart" -> top result is Walmart.com... no address to nearest Walmart to be found -> Close Safari -> Open Maps app -> search for Walmart

And it got so annoying to have those extra steps. I know I can change my workflow and get used to it. But it wasn't just directions. It was other basic searches. Like if I needed a phone number for a local business. It drove me crazy. I really hope Kagi gets better at those sort of things. I want them to succeed. But it was just too much friction for me.

Re:The next Google by richardsocher on Tuesday April 05, 2022 @04:39PM (#30924708)
We found similar issues at https://you.com a while back. We just had to be good for more query families. Now we have both the walmart locations in a map app, eg https://you.com/search?q=walmart and coding related useful results, eg. https://you.com/search?q=how%20do%20I%20find%20all%20files%2...

or https://you.com/search?q=pyspark%20filter%20array%20element

Re:The next Google by Ennea on Tuesday April 05, 2022 @04:50PM (#30924835)
Too bad you.com does not work in Firefox with the "beacon" function disabled (beacon.enabled set to false in about:config).
Re:The next Google by scim-knox-twox on Wednesday April 06, 2022 @04:05AM (#30929662)
I never even tried you.com because I see nothing (I don't enable JS for sites I don't trust).
Re:The next Google by richardsocher on Tuesday April 05, 2022 @05:51PM (#30925510)
Hi Ennea, Can you help me understand why you make this particular change in the config?
Re:The next Google by Ennea on Tuesday April 05, 2022 @06:20PM (#30925824)
To be perfectly honest, I cannot even remember making that change, but also couldn't find any info on whether Firefox or some extension may have done this. I will leave it disabled, however, because its purpose seems to be analytics, and opting out of (at least some of) them this way seems like a good idea.

Since disabling it this way removes the `sendBeacon` function from existence, you should just be prepared to properly handle its absence.

Re:The next Google by radicality on Tuesday April 05, 2022 @11:19PM (#30928113)
Is it always about analytics? Or is it ocassionaly also a useful API for other tasks?

I know little about front end JS dev, but the docs say it’s just a way to send an asynchronous request (no response) with a guarantee that the the request will be sent out, even if the page starts unloading. That’s apparently not a guarantee with the two other to send requests - XmlHttpRequest and fetch api.

Re:The next Google by 312c on Tuesday April 05, 2022 @11:33PM (#30928194)
The beacon api was created specifically to be a lightweight method for telemetry/logging
Re:The next Google by Gareth321 on Wednesday April 06, 2022 @03:54AM (#30929584)
I agree this disrupts my muscle memory, but if we're honest, that particular workflow isn't necessarily optimal. It's just what Google has trained us to do. If you're seeking directions to Walmart, the most efficient (and one might argue intuitive) method is to open your maps app directly, and type in "Walmart".
Re:The next Google by wanderingmind on Wednesday April 06, 2022 @12:40AM (#30928549)
Kagi supports DDG bangs. So just type `Walmart !g` and you will get the google search output
Re:The next Google by smk_ on Tuesday April 05, 2022 @04:02PM (#30924225)
I’ll do the same as well. Kagi has literally improved my life a significant degree.
Re:The next Google by href on Tuesday April 05, 2022 @02:31PM (#30922952)
Same. I switched to it for a day just to give it a try and I never switched back. Absolutely willing to pay if the quality stays the same.
Re:The next Google by josh_p on Tuesday April 05, 2022 @02:19PM (#30922809)
It's free while they're in beta. There's a "waitlist" but put your email on it and you'll get an invite within a week. Give it a try.

I've been using it for a couple weeks now on my work laptop and for programming-related searches its been great so far. And the usual annoyances that show up at the top of google and DDG don't show up on Kagi (geeks4geeks, etc).

Re:The next Google by dx034 on Thursday April 07, 2022 @03:31AM (#30941714)
The cost per search query is incredibly small. You could probably have <1% premium users. If your search engine is used by a billion people a day, 10 million paying users are still enough to pay a few thousand people developing your product (depending on your location).

I believe products can work that way, offer premium service and features for the very few that need it and a basic service to anyone else. In the end, the free tier is cheaper than what you'd have to spend on marketing otherwise.

Re:The next Google by TradingPlaces on Wednesday April 06, 2022 @09:47AM (#30931887)
I am a Kagi beta user, and I intend to pay when they start charging. I have wanted a paid ad/tracker-free Google for a decade now. I want to be the customer, not the product