salmon_protocol
Get flash to fully experience Pearltrees
louisgray.com: Proposed Salmon Protocol Aims To Unify Conversati
As comments on the Web become fragmented, conversations that occur on downstream aggregation sites often are taking place in a silo, disjointed from parallel discussions on the originating Web site. Over the last two years, many people have found this evolution controversial, hoping to unify the conversations in a central location - and some services, including JS-Kit's Echo and Disqus , have taken the first step by pulling external discussions to the source. But a brand new proposal, authored by John Panzer of Blogger , called the Salmon Protocol , is looking to take advantage of Pubsubhubbub to unify the conversations in all places, both upstream and downstream.
Salmon Protocol for Distributed, Real-Time Content Expands with
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 .Obviously the post has stirred some interest and generated a conversation. But the conversation is dispersed in many different places. Publisher looses track of many aspects of the conversation around the post.
