Personally, I'm very excited by Wave. I think it's going to be great (as in Google usually make quality stuff when they put their minds to it, I think it will be free enough to use with good conscience, and it will be uber-powerful)

I'm also willing to bet on the ultra-conservatism of the majority of users, and predict that they WON'T GET IT. This will have made hardly a dent on either email or M$ Office use by this time next year. Most people will be confused (rather than delighted) by the blurring of email, document editing and real time conversation. Early adopters won't be able to use it to send emails or share documents with late-adopters, so hardly anyone will be able to use it in enterprises etc.

The people who'll be most affected by this are 37 Signals, Huddle, SocialText etc. who are trying to sell web-based project management or enterprise blogs and wikis to early adopters. It's gonna be a tsunami in that market.

Nevertheless, can't wait to play with it.

Couple of interesting posts

How to add third party widgets to SocialText

Hat-tip Dennis Howlett Newsgator seem to be taking Yasn-as-platform into the enterprise.

He's also blogging about Wetpaint wiki + social publishing.

Very interesting article on the fact that there are no "neutral" markets or auctions (in the sense of not producing a prejudiced outcome)

Leads to and ties with a Tim O'Reilly on automated vs. human decision making

(hat-tip : SJ)

I'm not, myself, particularly entranced by all the "human improvements on automated search" (Mahalo, Knol, Squidoo) etc. I don't find myself thinking "I must find out about X but I don't trust Google to give me the right answer, I'll go and see if there are any experts over at ..." What I tend to do is start with Google, and find it's almost always sufficient for my requirements ... or at least starts me browsing in the right direction.

What Google *is* pretty lousy at is product recommendations (which is what so many of the rivals point out) but frankly going to a search engine and saying "what should I buy?" is pretty stupid. And ignores the fact that blogs do a pretty good job of that.

So I'm just not seeing all this "pain" that people claim to be having from Google being gamed by the SEOs.

Very obviously a PageRank type algorithm, even if it was working perfectly, wouldn't be the place to discover idiosyncratic, offbeat resources. The only way you're likely to find those is through a skilled editor / curator or interesting social network. But, again, blogs are already great for editor-curators. And maybe some other social networking services handle the social routing. In particular, one thing I'm noticing is that I'm getting a *lot* of good links flowing to me through Twitter.

Update : Wikia's problem is that no-one is going to understand it (I mean the process) in time for it to get useful or interesting.

Yellowikis

Aparently there's a wiki yellow pages for company information getting some publicity.

I have a personal interest here. I wrote a company registry module for Infoconomy back in 2000 (that site's running on Philip Greenspun's ACS). It was a good old-fashioned bit of relational modeling, handling international companies with HQs in different countries and multiple branches, categorization, partner and competitor relations etc.

When the site went live, the module was left out. No one, me included, could imagine that they'd launch with the small amount (around 50 companies skeletons, maybe 20 full profiles) of test data that had been entered during development. But researching, writing and entering the data was expensive. And this was a small startup magazine with a few journalists who realized that completing the catalogue was more work than they could handle.

Five years later, Infoconomy, and the CRM system (built by my friends on top of the ACS) seem to be still going strong. But, unless the company registry is hidden behind the subscription firewall, I don't think this feature ever did make it. Yellow-pages represent a great deal of work.

Can a wiki supplant that?

Here's what's good about a wiki. It's cheap. No one has to pay me to write a custom database application. If I was advising anyone who thought of building this kind of application, I'd start with a wiki as an internal prototype of the registry. I'd get them entering the data into wiki pages with some simple markup that could be scraped later.

I'm not quite prepared to stick my neck out and say I think Yellowikis will disrupt the yellow-pages industry. But I'd like to see it try.