<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Confirmed! Google Wave = Google Tsunami!</title>
	<atom:link href="http://www.whytwitter.co.uk/150/confirmed-google-wave-google-tsunami/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.whytwitter.co.uk/150/confirmed-google-wave-google-tsunami/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=confirmed-google-wave-google-tsunami</link>
	<description>Twitter Information, Twitter News, Twitter Spam, Social Marketing, Chrome OS, Netbook Pack</description>
	<lastBuildDate>Sun, 21 Feb 2010 03:27:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark O'Neil</title>
		<link>http://www.whytwitter.co.uk/150/confirmed-google-wave-google-tsunami/comment-page-1/#comment-15</link>
		<dc:creator>Mark O'Neil</dc:creator>
		<pubDate>Tue, 24 Nov 2009 19:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.whytwitter.co.uk/?p=150#comment-15</guid>
		<description>Personally, the concept makes a hell of a lot of sense, especially as an open platform play.

My simple net out is that this is a model that deals elegantly with both messages and payloads, where the payloads could be pics, videos, posts, songs, maps, people/product/business listings, etc.

As such, there is a lot of value in how the handling layer processes these messages/payloads, enabling them to be aggregated and/or filtered into logical constructs, like NOW, LOCAL, TYPE, POPULAR, VIRAL, ENGAGING, etc.

I blogged about an application model that is very complimentary to this (and for which I have modeled out six very specific use cases) in a post called:

“Right Here Now” services: weaving a real-time web around status


Mark</description>
		<content:encoded><![CDATA[<p>Personally, the concept makes a hell of a lot of sense, especially as an open platform play.</p>
<p>My simple net out is that this is a model that deals elegantly with both messages and payloads, where the payloads could be pics, videos, posts, songs, maps, people/product/business listings, etc.</p>
<p>As such, there is a lot of value in how the handling layer processes these messages/payloads, enabling them to be aggregated and/or filtered into logical constructs, like NOW, LOCAL, TYPE, POPULAR, VIRAL, ENGAGING, etc.</p>
<p>I blogged about an application model that is very complimentary to this (and for which I have modeled out six very specific use cases) in a post called:</p>
<p>“Right Here Now” services: weaving a real-time web around status</p>
<p>Mark</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- www.000webhost.com Analytics Code -->
<script type="text/javascript" src="http://analytics.hosting24.com/count.php"></script>
<noscript><a href="http://www.hosting24.com/"><img src="http://analytics.hosting24.com/count.php" alt="web hosting" /></a></noscript>
<!-- End Of Code -->
