Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kagi Translate

blog.kagi.com

Post reply on HN
Print view View original

91–100 of 119 posts

Re: Kagi Translate

#91

Post by ac29 »

Aachen wrote: post #48
erinnh wrote: post #40

Kagi develops lots of features, but they seem to often be quarter-baked. Maps for example is basically unusable and has been for a while. (at least in Germany) Trying to search for an address often leads Kagi maps to go to a different random address. Still love the search, but Id love for Kagi to concentrate on one thing at a time.

Where do I find the map feature? I'm curious to see if I can identify what data source and search software it is based on, since I've heard similar complaints about Nominatim and it is indeed finicky if you made a typo or don't know the exact address; it does no context search based on the current view afaik. Google really does do search well compared to the open source software I'm partial to, I gotta give them that…

> I'm curious to see if I can identify what data source and search software it is based on

Kagi uses Apple Maps

Re: Kagi Translate

#92

Post by LargoLasskhyfv »

Aachen wrote: post #22

I can't use it because I'm not classified as "human" by a computer. There is no captcha that I could get wrong, just a checkbox that probably uses a black box model to classify me automatically Was curious after the post claimed that the quality is better than Google and DeepL, but the current top comment showed translations from Afrikaans that it got wrong but I could understand as a Dutch person who doesn't even sp…

Zalgorythmz on crack. Brainz out of whack.

(cf. https://en.wikipedia.org/wiki/Zalgo_text https://en.wikipedia.org/wiki/Zombie https://en.wikipedia.org/wiki/Crack_cocaine )

Re: Kagi Translate

#94

Post by freediver »

lurking_swe wrote: post #90
freediver wrote: post #50

Earlier quoted context omitted.

We are focusing most our resources on search (which I hope you can agree, we are doing a pretty good job at). And it turns out search is not enough and you need other things - like maps (or a browser, because some browsers will not let you change search engine and our paid users can not use the service). Both are also incredibly hard to do right. If it appears quarter-baked (and I am first to say that we can and will…

love the plan, but i’d suggest being more up front with users on how “finished” a product is. With the maps example, you run into problems because of expectations. If you slap a BETA or ALPHA logo on the maps product, expectations will be lower, and people are more forgiving of issues while you continue improving the product. Or if it’s only good in the US (just an example), make it clear somehow when searching for a…

Interestingly we do not get a lot of bug reports for Maps on our feedback forum. And this is where we tend to go to look for problems to fix.

Re: Kagi Translate

#96

Post by dgacmu »

freediver wrote: post #94
lurking_swe wrote: post #90

Earlier quoted context omitted.

love the plan, but i’d suggest being more up front with users on how “finished” a product is. With the maps example, you run into problems because of expectations. If you slap a BETA or ALPHA logo on the maps product, expectations will be lower, and people are more forgiving of issues while you continue improving the product. Or if it’s only good in the US (just an example), make it clear somehow when searching for a…

Interestingly we do not get a lot of bug reports for Maps on our feedback forum. And this is where we tend to go to look for problems to fix.

As a paying Kagi user, in my case, that's because I !g any query that I expect to give local results for, and I often go directly to maps.google.com for map results. The general search results are awesome, particularly in my tech bubble, since I don't have to see w3schools garbage and the like. Localized stuff, not so great, and maps I prefer to avoid.

(Edited to add: Though perhaps I should give maps a try again. They seem to have gotten better since I formed my muscle memory.)

Re: Kagi Translate

#97

Post by nine_k »

ynoxinul wrote: post #24
pentacent_hq wrote: post #14

I recently noticed that Google Translate and Bing have trouble translating the German word "Orgel" ("organ", as in "church organ", not as in "internal organs") to various languages such as Vietnamese or Hebrew. In several attempts, they would translate the word to an equivalent of "internal organs" even though the German word is, unlike the English "organ", unambiguous. Kagi Translate seems to do a better job here. I…

Google Translate often translates words through English.

The dearth of Lojban and Ithkuil texts holds back machine translation, for they would be perfect intermediate languages.

Re: Kagi Translate

#98

Post by wenc »

krackers wrote: post #3

How is this compared to using gpt-4 directly?

ChatGPT does better -- it picks up context and produces more idiomatic output.

Kagi translate does pick up context (for instance, "Anne is older than her sister Carmen" is a good test for languages that have different words for older and younger sister -- Google Translate gets this wrong all the time).

But the Kagi output is stilted and grammatically incorrect for say, Cantonese.

Re: Kagi Translate

#99

Post by esperent »

freediver wrote: post #94
lurking_swe wrote: post #90

Earlier quoted context omitted.

love the plan, but i’d suggest being more up front with users on how “finished” a product is. With the maps example, you run into problems because of expectations. If you slap a BETA or ALPHA logo on the maps product, expectations will be lower, and people are more forgiving of issues while you continue improving the product. Or if it’s only good in the US (just an example), make it clear somehow when searching for a…

Interestingly we do not get a lot of bug reports for Maps on our feedback forum. And this is where we tend to go to look for problems to fix.

As a paid kagi user, that might be because I tried kagi maps once, went "yep that's crap" and from then on went to Google for any maps related search.

However, I neither expect nor need kagi to have a perfect replacement for every single google product. I'd rather it focus on creating better versions of the things that google is bad at (especially basic search) rather than trying to provide bad versions of the things Google is good at (maps, translate).

Re: Kagi Translate

#100

Post by laserbeam »

freediver wrote: post #94
lurking_swe wrote: post #90

Earlier quoted context omitted.

love the plan, but i’d suggest being more up front with users on how “finished” a product is. With the maps example, you run into problems because of expectations. If you slap a BETA or ALPHA logo on the maps product, expectations will be lower, and people are more forgiving of issues while you continue improving the product. Or if it’s only good in the US (just an example), make it clear somehow when searching for a…

Interestingly we do not get a lot of bug reports for Maps on our feedback forum. And this is where we tend to go to look for problems to fix.

As a kagi early adopter… why would I bug report on a feature I actively avoid using?

I can totally recommend search to anyone, but I agree with others in this chat that most toys feel beta. I’m glad to have them but can’t recommend them.

For maps, your goals of being ad free go against what I need from maps search. 90% of the time I search for restaurants, museums, businesses, opening hours, phone numbers of various local shops. People add that data to google, and not that many other maps services :(. That is where they advertise how to be contacted. Addresses and directions are really secondary to a maps search.

Post reply on HN