4 ms·

I also have a fun one: https://www.google.com/search?q=%22ketmax%22+zip https://www.google.com/search?q=%22ketmax%22+zip It's hilarious because it's now gotte

I also have a fun one: https://www.google.com/search?q=%22ketmax%22+zip https://www.google.com/search?q=%22ketmax%22+zip It's hilarious because it's now gotten to the point where the only non-noise results are the ones where I'm describing how the query in question is broken. In fact, the top result I'm seeing here is a perfectly-paraphrased oneliner - Google is describing its own brokenness! :D (I must admit, I'm impressed to see such a perfect summary of the situation presented in a single paragraph like that. Google picked exactly the right portion of the sentence. I take it there's really nothing out there in open-source land that does anything like that, is there? :( )

TimJYoung 9y ago
I think they just picked the sentences that contained the keywords, and concatenated them together (if necessary because the sentences are in two different locations). The sentences themselves can be found using basic word searches once the content is parsed/indexed (obviously, the Google indexing/searching is more complicated than that). Both of my company's database engine products offer this type of functionality, as do many database engines/servers out there. It's typically referred to as full-text indexing or full-text searching: https://www.postgresql.org/docs/9.5/static/textsearch.html https://www.postgresql.org/docs/9.5/static/textsearch.html and there are lots of ways to control how/why certain words are indexed/search (stop words, synonyms, stemming, etc.). With the right amount of customization, you can get pretty close to ideal search results.