4 ms·

Main two bits: 1. Is there a way to force off the typo correction? I tried "smartos" both with and without quotes, and either way I get results for the word "s

by mjn 13y ago

Main two bits: 1. Is there a way to force off the typo correction? I tried "smartos" both with and without quotes, and either way I get results for the word "smartest", which aren't about SmartOS (an operating system derived from OpenSolaris). 2. In terms of CSS/font/layout, honestly I like hnsearch.com's results better. I think part of it is that I use hnsearch.com as an alternative HN interface, not just a search engine, and it's usable for that purpose, in part because it looks more like regular HN. The issue for me more generally is that hnsearch.com is almost perfect as an HN search engine, as far as I'm concerned. It does what I want, does it fast, with good coverage and a usable interface. So my advice for alternatives would tend towards just "yeah, make it more like that", which is maybe not the most useful commentary.

redox_ 13y ago
1. For now, there isn't any way to force off the typo correction. It has been added to our feature requests list. 2. What do you think about http://hn.algolia.com/legacy#!/story/forever/0/algolia http://hn.algolia.com/legacy#!/story/forever/0/algolia or http://hn.algolia.com/legacy#!/all/sort_by_date/0/story:7126301 http://hn.algolia.com/legacy#!/all/sort_by_date/0/story:7126... ?
- mjn 13y ago
 The 'legacy' mode is pretty nice, thanks! Does what I want for the HN-browsing (vs. searching) use-case, no real complaints. Minor bug: the results highlighting seems to break links. For example try this search: http://hn.algolia.com/legacy#!/comment/forever/0/algolia http://hn.algolia.com/legacy#!/comment/forever/0/algolia. The link in the first comment ends up being turned into http://twittersearch.algolia.io http://twittersearch.algolia.io
 - redox_ 13y ago
 We've just improved the links highlighting and have deployed it to production. Thank for the bug report!
 - mjn 13y ago
 Looks good! Another bug report, though I'm not sure if this is on your side or an issue with the data HN is feeding: it looks like you're indexing even killed/dead HN stories, which leads to a lot of spam on some queries. Example: https://hn.algolia.com/?q=air+max#!/story/forever/0/air%20max https://hn.algolia.com/?q=air+max#!/story/forever/0/air%20ma...
 - redox_ 13y ago
 I'm on it.
dclara 13y ago
I guess the word "smartos" is not found, then the typo correction results are shown instead. I like the hnsearch.com too, but that will be shutdown soon. The interesting thing to me is they are using ThiftyDB which is a full-text database providing fast performance instead of the file-based search. I think the files have the indexes, but they are not scale if not using some kind of database on the backend. Somehow the fast response to the key strike is not that preferred. Google provides autocomplete for the keywords when we are typing. hnsearch.com just let user to finish want they want to search. They are ok to me.

by mjn 13y ago

redox_ 13y ago

1. For now, there isn't any way to force off the typo correction. It has been added to our feature requests list. 2. What do you think about http://hn.algolia.com/legacy#!/story/forever/0/algolia http://hn.algolia.com/legacy#!/story/forever/0/algolia or http://hn.algolia.com/legacy#!/all/sort_by_date/0/story:7126301 http://hn.algolia.com/legacy#!/all/sort_by_date/0/story:7126... ?

mjn 13y ago
The 'legacy' mode is pretty nice, thanks! Does what I want for the HN-browsing (vs. searching) use-case, no real complaints. Minor bug: the results highlighting seems to break links. For example try this search: http://hn.algolia.com/legacy#!/comment/forever/0/algolia http://hn.algolia.com/legacy#!/comment/forever/0/algolia. The link in the first comment ends up being turned into http://twittersearch.algolia.io http://twittersearch.algolia.io
- redox_ 13y ago
 We've just improved the links highlighting and have deployed it to production. Thank for the bug report!
 - mjn 13y ago
 Looks good! Another bug report, though I'm not sure if this is on your side or an issue with the data HN is feeding: it looks like you're indexing even killed/dead HN stories, which leads to a lot of spam on some queries. Example: https://hn.algolia.com/?q=air+max#!/story/forever/0/air%20max https://hn.algolia.com/?q=air+max#!/story/forever/0/air%20ma...
 - redox_ 13y ago
 I'm on it.

dclara 13y ago

I guess the word "smartos" is not found, then the typo correction results are shown instead. I like the hnsearch.com too, but that will be shutdown soon. The interesting thing to me is they are using ThiftyDB which is a full-text database providing fast performance instead of the file-based search. I think the files have the indexes, but they are not scale if not using some kind of database on the backend. Somehow the fast response to the key strike is not that preferred. Google provides autocomplete for the keywords when we are typing. hnsearch.com just let user to finish want they want to search. They are ok to me.