*Techcrunch was WRONG about Wikiasari*
Posted by rexdixon on December 24, 2006
As I stated yesterday, as well as TechCrunch where I saw the information, it’s apparent that that TechCrunch may have had it all WRONG. According to Jim Wales, who should know since Wikia is his baby, the best place to go is right here. This is where you will find the real deal – The Wikia Search Project.
Technically Speaking, I guess this goes to show you – you just can’t believe everything you read. I will say in Michael Arrington’s defense, he is usually dead on about 99% of the time.
Technically Speaking 
Michael Arrington said
let’s see how this plays out. My source was pretty darn good. It’s clearly a screen shot of a wikia/wikipedia product, and it happens to match what they are describing exactly. My guess is that it is an old version of what they are working on.
rexdixon said
Michael – No offense to you at all, just wanted to post what I knew. I guess we can kick back now and see. – Rex
Good luck with the Google-killing, Jimbo » Mathew Ingram: mathewingram.com/work said
[…] Mike Arrington posted what he says is an exclusive screenshot of a Wikia search page, but Jimmy Wales has said that Mike’s post is all wrong and that the screenshot has nothing to do with what he’s working on. In a comment on Rex Dixon’s blog, Mike says that his source is pretty good and he thinks what he saw was an early version of Wiki Search. […]
The Software Abstractions Blog said
Wikipedia Search to compete with Google
Jimmy Wales, founder of Wikipedia, has announced that his for-profit company, Wikia Inc, will be launching an internet search engine to compete with Google and Yahoo!. According to the Times of London : Mr Wales has begun working on a
Kyong Berrell said
Hello I wasLooking out a few sites on baidu and i found your post. I have to that you have a great site here. You’re blogging is quality and now a days ya do not find that on too many sites. Keep up the great job and I willmost definitelyhave bookmarked you. Once again thank you. and have a amazing day!
JERRY said
@kelownagurl A couple of users (early Twitter adopters) encountered such an error. Basically the API call hangs instead of returning data.