3 ms·

> Interestingly, with the Ambulance search I see: Right, that's a legit page info for that movie. But your search engine doesn't actually extract the answer to

by jsnell 5y ago

> Interestingly, with the Ambulance search I see: Right, that's a legit page info for that movie. But your search engine doesn't actually extract the answer to my question ("releases april 8th") from the page, and this should have been about as easy as it gets. The answer happens to be in the snippet, but the snippet is unreadable. Now, I wasn't seriously expecting you to have localization of results at this point, but the query wasn't meant to trip the system up either. I only realized this wasn't a globally synchronized release date when comparing the results. (And again, this was about the easiest possible case for localization. IMDB has a page with structured data for release dates by country, and you clearly are using geolocation for the query that produced local weather results.)

jedwhite 5y ago
Yes any localization is very much a future feature. There are some small functions that use it that are things our user community has asked for, but we're very much taking an iterative approach. I think with a small team you have to do that, and accept that early on you can't do everything but that you can keep iterating and improving quickly based on the things that users say are most important. The most important feature for our early users so far, based on the feedback we get, is factual information question answering, and there are some classes of query where Andi is already very useful. And as it gets better we hope it can save people a lot of time. Reader view is popular for the same reason because it saves people time and distraction. At the same time, I think everyone (myself included) likes to play "let's trip up the AI" with something new like this, and it's fun and a great way to get training data and share a laugh on our Discord. When we don't log searches, it's some of the most valuable data we can get :)

by jsnell 5y ago

jedwhite 5y ago

Yes any localization is very much a future feature. There are some small functions that use it that are things our user community has asked for, but we're very much taking an iterative approach. I think with a small team you have to do that, and accept that early on you can't do everything but that you can keep iterating and improving quickly based on the things that users say are most important. The most important feature for our early users so far, based on the feedback we get, is factual information question answering, and there are some classes of query where Andi is already very useful. And as it gets better we hope it can save people a lot of time. Reader view is popular for the same reason because it saves people time and distraction. At the same time, I think everyone (myself included) likes to play "let's trip up the AI" with something new like this, and it's fun and a great way to get training data and share a laugh on our Discord. When we don't log searches, it's some of the most valuable data we can get :)