redox_

Well done!

yes hn.algolia.com is powered by Cloudflare /o\

Sure thing, we’re experimenting with some Load-Balancing heuristics and instrumentations, and it looks it got rate-limited by the engine who got surprised all traffic was coming from a single IP /o\

Let’s say it was a mix of HN alerting (hnwatcher), good timing (Friday evening) and luck :) very happy to have seen this in time. Have a nice WE as well!

Should be good now.

Should be good now.

[HN Search admin speaking] We disabled the rate-limit for now. A load-balancer experimentation that didn't behave as expected (the LB's IP getting rate-limited).

Thanks for sharing, this is surprising as the rate-limit should be per IP :/ Investigating.

Investigating, this is weird as the rate-limit should be per IP :/

Is it? Working from here. What kind of network error do you get?

Do you think about any improvement I could share with our team? I know they're always looking for feedback to improve the HN Search experience.

Oh that's weird, a dropdown menu should appear and give you access to a list of developer resources :/

Btw, part of this pricing rework is also about removing some of the feature gating. It's an approach we've taken to really get the feature right, first releasing it to a smaller set of (larger) customers before opening it up to the whole mass.

(Sylvain from Algolia speaking) Thanks for sharing, our pricing & its transparency is actually something we are working on right now to address this perception. We've been iterating a few times already over the past 7 years, but this is one more signal for us to act!

The reality is that based on the number of objects you want to search in, your search traffic, your searches' complexity and your index/relevance configuration; the underlying resources can vary soo much, it's hard to have a single pricing that fits all use-case.

Yes, when sorting by date it's currently configured to disable typo-tolerance. This is to avoid having an old (but approximative, with typos) result BEFORE the correct ones.

You should give it a try; Algolia has a FREE tier you can play with. You can also watch this 45sec video to get a grasp of it: https://youtu.be/IYY5RM1sBC0

Correct, and the source code is here: https://github.com/algolia/hn-search

Yes, when sorting by date it's currently configured to disable typo-tolerance. This is to avoid having an old (but approximative, like with typos) result BEFORE the correct ones.

Congrats Algolia!

Algolia's engine relies on an optimised Damerau-Levenshtein + prefix matching algorithm.

Would love to merge any PR you would think about for adding a dark theme to our GH repository: https://github.com/algolia/hn-search

The team has been testing a new ranking formula, keeping you posted tomorrow.

Definitely aligned with that, and having a technical development path is something we do provide.

Still, some managers are happy (and good at) managing a team of 6-8 but are wondering about their next steps. Is you management career just about getting more direct reports and ultimately managing managers? or something else?

Thanks for sharing, this is a good example where the first 2 hits on Algolia have a "better" textual relevancy (proximity between words is better, because of the "-based" word in the middle) but where the 3rd hit is most probably the one we want to see first because it has more than 100 points while the 2 others have 3.

Let me share that to the team and see whether we can try something.

Hey latch, I've been working on the Algolia-based HN search and would love to improve it to provide you with a better search experience.

Do you think about any specific improvements? Would you mind sharing with us some non-working queries? We can follow-up here and you can also open issues on https://github.com/algolia/hn-search

(I'm an Algolia employee) We don't plan to add classification but would love to partner with anyone willing to work on it, providing them with access to GH repositories and/or API tokens. Let us know through our support channels.

Not sure why, but you need to remove the Ad-Blocker to see our CTO (Julien)'s answer /o\

(algolia employee) Hi Chris, Algolia is actually not using Elasticsearch. We've been building our own search engine from the ground up to target the very (end-)user-facing search use-case (big focus on UX, speed & typo-tolerance) while one of Elasticsearch's sweet spot is more billion of line of logs indexing, aggregations & filtering.

You can read more about the differences on Quora, our CTO answered there a few years ago: https://www.quora.com/How-does-Elasticsearch-relate-and-or-c...

(algolia employee speaking) Please don't hesitate to reach out to us using support@algolia.com, we would love to better understand your issues and ultimately improve the relevancy.

You should submit a GitHub issue here: https://github.com/algolia/hn-search/issues

I'm wondering whether the http://hn.algolia.com/opensearch.xml configuration could help here, might need to tweak it a bit.