background preloader

TechCrunch Disrupt May 2010

Facebook Twitter

TechCrunch Disrupt Sponsors

GE + YOU = AWESOME - Google Moderator. Disrupt » HACK DAY. Disrupt » PLAY. TechCrunch Disrupt. The Third Disruptive Wave #tcdisrupt. Warning: Long post ahead. If you just want the trailer, it’s this – “Everything is changing. Again.” Tomorrow morning we’ll kick off our most ambitious event to date, TechCrunch Disrupt, in New York. The event is sold out, but we’ll have tens of thousands of people also tuning in to the livestream of the three day event.

If you’re not attending, watch that livestream from the comfort of your office, living room or wherever it is that you people spend your time. We’ve called the event TechCrunch Disrupt, but we weren’t thinking about the name as a theme for this particular event. And yet, as I have conversations with the launching startups and the amazing speakers lined to to talk at Disrupt, it’s become clear to me that we are indeed in a massively disruptive moment. These conversations are why, for the first time, I am extremely nervous to go on stage tomorrow morning. Until the last few days it hasn’t crystalized for me. Before I dive deeper, here’s a taste of what I’m talking about. Twitter search #tcdisrupt. Battlefield at TechCrunch Disrupt. Soluto – Anti-Frustration Software. UJAM - coming soon. Betterment.

FluidDB. Image: Jin Wicked One way to use Fluidinfo, among many, is as a universal engine for metadata. I’ll have to explain what I mean by that, especially seeing as some people got the impression from the earlier post on data vs metadata that we don’t think metadata is important, or that it doesn’t exist, or similar. I tried to make it clear in the post, and in responding to the comments that followed, that that’s not what was meant: In fact that’s one of the major initial goals of Fluidinfo – to be a metadata engine for everything.

So that’s how important we think metadata is! The way to support metadata on anything is to have an underlying architecture that’s flexible enough to allow that to happen – without someone setting the thing up with an a priori determination of what’s meta- and what’s not. True support for metadata is too important for that – to do it properly you need the architecture to be neutral. The question is: how can Fluidinfo be used as a universal metadata engine? Stay tuned. Off & Away | We're Launching Soon! Appbistro. LiveIntent - Recommending the best of the social web. Video Genie. Audioo. Publish2. Textingly.

Compass Labs. WeReward. Geotoko. ChompOn Deals: Exclusive Local Dining and Entertainment Offers. Tickreel. Plantly. Movieclips.com. Keenkong. Art.sy - The place to discover and share original fine art onlin. Live Matrix: Home. NoiseToys - Music Is Meant To Be Played.