redox_

20 ms·

211.
by redox_ 13y ago
We've just improved the links highlighting and have deployed it to production. Thank for the bug report!
212.
by redox_ 13y ago
What do you think about http://hn.algolia.com/legacy ?
213.
by 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 or
214.
by redox_ 13y ago
The issue with the back button seems to be a Chrome rendering bug. I've work-arounded it by scrolling to top on the first query, but I'm still looking for a more elegant way to fix it. (Will be deployed later today)
215.
by redox_ 13y ago
1. Sorting by date and not by points often produces ugly results (especially on long period) so we introduced the "last 24", "past week" and "past month" options filtering the resultset but keeping the default
216.
by redox_ 13y ago
All feedback are read and welcome :) We've already deployed a few UX improvements and are currently working on improving the usability. We'll deploy it soon, preview available here: https://hn.algolia.com/beta .
217.
by redox_ 13y ago
Yes, that's a consequence of our typo-tolerance handling. We're computing a damerau-levenshtein edit-distance and are currently allowing 2 typos if the word is at least composed by 7 chars. Regarding the corpus, we'll probabl
218.
by redox_ 13y ago
I've just deployed a new version based on your feedback. We'll continue to improve it. Thanks for your help.
219.
by redox_ 13y ago
For now, the ranking is only based on the number of points/comments of an item. We're actually working on a way to include the freshness of a post. Thanks for the support ;)
220.
by redox_ 13y ago
Yes I've noticed the same strange issues using Chrome. Working on it.
221.
by redox_ 13y ago
Right, working on it.
222.
by redox_ 13y ago
Thank you for the feedback, we'll improve it based on all of them in the next few days.
223.
by redox_ 13y ago
Yes maybe. Anyway, good job!
224.
by redox_ 13y ago
You revealed a secret key in your README, is that OK?
225.
by redox_ 13y ago
Was using homebrew, composer & bundler... FAIL; github I need you!
226.
by redox_ 13y ago
The blog post about how I've implemented it: http://blog.algolia.com/improving-ranking-twitter-handles-se...
227.
by redox_ 13y ago
Thanks. Sure it has, I explain what (and how) I improved here: http://blog.algolia.com/improving-ranking-twitter-handles-se...
228.
by redox_ 13y ago
I've just committed a patch skipping top users if the match was only in the description, with typos. Thanks for your feedback.
229.
by redox_ 13y ago
You're right "Ryan Seacrest" has +10M followers. As you might have read on the blog, the user query produces 2 underlying queries. The first targeting top users (having 10M+ followers). This one retrieves "Ryan Seacrest&
230.
by redox_ 13y ago
Demo is available at http://twittersearch.algolia.io
231.
How I improved Twitter Handles Search's ranking(blog.algolia.com)
6 points by redox_ 13y ago|4 comments
232.
by redox_ 13y ago
Drupal?!
233.
Evolution of iOS 7 (beta—.0—.1)(twitter.com)
1 points by redox_ 13y ago|0 comments
234.
Wikimedia moving to Elasticsearch(blog.wikimedia.org)
1 points by redox_ 13y ago|0 comments
235.
Apple’s App Store has best year ever in 2013; tops $10B(gigaom.com)
1 points by redox_ 13y ago|0 comments
236.
by redox_ 13y ago
I released http://twittersearch.algolia.io/ :)
237.
Everything you wanted to know about JavaScript scope(toddmotto.com)
2 points by redox_ 13y ago|0 comments
238.
by redox_ 13y ago
And how did you configured your columns?
239.
Ask HN: how do you read your noisy Twitter stream?
5 points by redox_ 13y ago|7 comments
240.
by redox_ 13y ago
BTW, raw data are available at http://dumps.wikimedia.org/other/pagecounts-raw ;)

More ›