ReadWriteWeb

The Internet is a mess these days.

Conversations are distributed and fragmented; a blog post's comments will almost surely appear on a number of sites other than the author's blog. Considering factors from Facebook shares, likes, and posts to comments on Google Reader or even content curators such as Hacker News, site owners have found it increasingly difficult over the past year or so to efficiently and effectively collect all the sentiments, media, entities, and data associated with any given piece of content. Salmon is a protocol that addresses this specific issue, and engineer John Panzer has begun an open-source project to help unify the conversations of the synaptic web.

Microblogging represents the first wave in the enterprise. Now the questions is what represents the second wave and how adoption will occur.

The issue of the second wave came back up again and again in "Applying The Real-Time Web in the Enterprise," at the ReadWrite Real-Time Web Summit today.

No one is getting Web aggregation quite right. That's one of the big take-aways from "Web Aggregation: What Works, What Doesn't," one of the breakout sessions at the ReadWrite Real-Time Web Summit.

We first heard about the fire hose meme several years ago in discussions about RSS. It was often used as a way to describe how information comes to you in a feed. The context has changed as real-time data becomes pervasive, and the questions about its volume persists.

Similar to the real-time stream itself, ReadWriteWeb's Real-Time Web Summit dares to tackle a collective stream of consciousness. As the official live bloggers, the ReadWriteWeb team is aggregating some of today's highlights. One of the great things about this event is that many of the disparate voices in the stream are meeting face to face (or in the flesh) for the first time. Naturally, this morning's event sessions included a discussion about location-based real-time data.