Technically Speaking

Rex Dixon – Professional BlogCaster

*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.


6 Responses to “*Techcrunch was WRONG about Wikiasari*”

  1. 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.

  2. 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

  3. […] 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. […]

  4. 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

  5. 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!

  6. JERRY said

    @kelownagurl A couple of users (early Twitter adopters) encountered such an error. Basically the API call hangs instead of returning data.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: