Interesting state of The Mechanical Turk roundup.

This especially important :

For most users of mechanical turk (us included), it has become an API call that fits smoothly within their workflow. (Or as someone at the meetup wryly suggested, turk is a Remote Person Call.) The last pair of speakers, Lilly Irani and Six Silberman, reminded us that behind mechanical turk lies thousands of workers† ("the crowd in the cloud") working without (health care) benefits, oftentimes at extremely low hourly wages. Irani and Silberman suggested that rather than abstracting mechanical turk services as mere API calls, users should start thinking of the plight of the turks ("Mechanical Turk Bill of Rights") behind the service. As a first step they have a released a Firefox plugin that aims to narrow the information assymetry between the turks (those performing task) and requesters (those posting tasks). While requesters can see ratings for turks, requesters aren't rated: Turkopticon lets turks rate requesters. They need more turks to download and start using Turkopticon, so if you know any mechanical turks please enourage them do so.

Meanwhile, even Intel seem to be trying to get into the netbook OS game with Moblin.

Mike Loukides :

Google is providing the idea leadership that the Java community needs.

Mark Sigal :

I have harped repeatedly (HERE and HERE) about the fact that the next version of the iPhone OS (and the underlying SDK) will allow third-party hardware accessory makers to build external hardware accessory offerings that take advantage of the software, service and hardware capabilities of the iPhone and iPod touch platforms.

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