I am in the process of transitioning over a brand spanking new lightning fast search engine for KMC.
Due to this transitioning process new posts won't enter the search engine until we go fully live. This should be by the weekend.
As of right now, "find all posts" is the only search using this new search engine. By the weekend, we shall get rid of the Google search and make vB search the default again. And hopefully "search by thread" should be here aswell.
Awesome the google search is pretty much all but useless, because on the off-chance you actually DO find what you're looking for, it simply gives you the thread it found it in. Not much help there when it's a large thread and you're looking for a certain post.
New search is up and running and blindingly fast. There are some new advanced operators you can use in your search:
userid: search by user - so userid:1 will only return results by me. You can get the userid of a user by looking at the URL from the profile of the person you want to search by. Or by entering the username in the advanced section of the search.
forumid: search by forum - so forumid:61 will only return results from the OTF. You can get the forumid by looking at the URL of the forum.
threadid: search by thread - so threadid:10813 will only return results from the "Random Comments" thread (our largest on KMC). You can get the threadid again by looking at the URL of the thread.
title: search by title - title:google will return all threads with the word google in them.
Only thing left is "results as thread" option, which will be done by the end of this week.
A max 3 hour delay is in place, because the index is updated every 3 hours. There is a alternative for mods - check my notes thread in the lounge. I've had a look at adding this, but due to the way the posts are indexed, I'll have to come up with an advanced solution to showing true "results as threads".
It would be nice to have a list of all the search operators, their functions, and a single example for each operator.
One thing I did find useful was the comma. It appears that the comma is used to specify multiple string searches similar to "piping" the results of an awk command through a second awk command in linux.
Double edit - I just tried some of the searches using the proper syntax and it appears not to be implemented or specifically disabled. "AND" "&&" "||" "OR" and such are not usable options. It says improve characters are present. I am a sad bear.
Last edited by dadudemon on Jul 3rd, 2011 at 04:20 PM