<?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: 2006 Predictions 15 and 16</title>
	<atom:link href="http://mobhappy.com/blog1/2006/01/04/2006-predictions-15-and-16/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobhappy.com/blog1/2006/01/04/2006-predictions-15-and-16/</link>
	<description>Russell Buckley and Carlo Longino on mobile technology.</description>
	<lastBuildDate>Tue, 22 May 2012 09:13:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Andy Tiller</title>
		<link>http://mobhappy.com/blog1/2006/01/04/2006-predictions-15-and-16/comment-page-1/#comment-57</link>
		<dc:creator>Andy Tiller</dc:creator>
		<pubDate>Thu, 05 Jan 2006 15:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://p6.hostingprod.com/@mobhappy.com/blog1/?p=51#comment-57</guid>
		<description>Definitely agree with your proposed sharing scenario.  The main issue is the cost of notifying your friends when you&#039;ve posted stuff (someone has to pay for those SMS messages).

In places where the recipient pays (e.g. the US), you could upset some of your friends if you post too often to your photo sharing site, causing them to receive lots of SMS notifications.  

In places where the sending party pays, then the service provider has to bear the cost directly, or pass it on to the end user.  (This is presumably why Yahoo!&#039;s free RSS-to-SMS service is only available in the US.)

IMS / SIP could potentially help solve this in future, with the possibility for a server to establish a direct connection to a mobile handset in order to push data to it.

On a related point, Cognima is building two-way data replication features into a future version of &lt;a href=&quot;http://www.shozu.com&quot; rel=&quot;nofollow&quot;&gt;ShoZu&lt;/a&gt;.  For example, when people visit your photostream on the
web and leave comments, you will be able to read the comment thread in the
ShoZu application on your phone.  Comments are queued on the server and sent down to the phone whenever it connects (e.g. for a photo upload).  The main benefit to users is that they can read comments on the move without having to
log in (via the phone browser) and check their account manually on
the off-chance that someone has left new comments (which, of course, often results in disappointment).

</description>
		<content:encoded><![CDATA[<p>Definitely agree with your proposed sharing scenario.  The main issue is the cost of notifying your friends when you&#8217;ve posted stuff (someone has to pay for those SMS messages).</p>
<p>In places where the recipient pays (e.g. the US), you could upset some of your friends if you post too often to your photo sharing site, causing them to receive lots of SMS notifications.  </p>
<p>In places where the sending party pays, then the service provider has to bear the cost directly, or pass it on to the end user.  (This is presumably why Yahoo!&#8217;s free RSS-to-SMS service is only available in the US.)</p>
<p>IMS / SIP could potentially help solve this in future, with the possibility for a server to establish a direct connection to a mobile handset in order to push data to it.</p>
<p>On a related point, Cognima is building two-way data replication features into a future version of <a href="http://www.shozu.com" rel="nofollow">ShoZu</a>.  For example, when people visit your photostream on the<br />
web and leave comments, you will be able to read the comment thread in the<br />
ShoZu application on your phone.  Comments are queued on the server and sent down to the phone whenever it connects (e.g. for a photo upload).  The main benefit to users is that they can read comments on the move without having to<br />
log in (via the phone browser) and check their account manually on<br />
the off-chance that someone has left new comments (which, of course, often results in disappointment).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave's Football Blog</title>
		<link>http://mobhappy.com/blog1/2006/01/04/2006-predictions-15-and-16/comment-page-1/#comment-56</link>
		<dc:creator>Dave's Football Blog</dc:creator>
		<pubDate>Wed, 04 Jan 2006 17:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://p6.hostingprod.com/@mobhappy.com/blog1/?p=51#comment-56</guid>
		<description>I really enjoy mobile blogging.  I&#039;ve been blogging NFL games from sports bars all season, using my Treo 650 and an IR keyboard.  I&#039;m able to take snapshots, upload them to my web site via FTP, and post them to the blog within minutes.  If I had EVDO, FTP would be faster, of course, but I wanted to jump on the smartphone bandwagon before the season started.

Not everyone has a Treo, though, and mobile blogging won&#039;t take off unless the carriers and/or phone makers provide enough tools to help people post snapshots and text to the web in real time.  We may see some very interesting apps in the next year or two, though.</description>
		<content:encoded><![CDATA[<p>I really enjoy mobile blogging.  I&#8217;ve been blogging NFL games from sports bars all season, using my Treo 650 and an IR keyboard.  I&#8217;m able to take snapshots, upload them to my web site via FTP, and post them to the blog within minutes.  If I had EVDO, FTP would be faster, of course, but I wanted to jump on the smartphone bandwagon before the season started.</p>
<p>Not everyone has a Treo, though, and mobile blogging won&#8217;t take off unless the carriers and/or phone makers provide enough tools to help people post snapshots and text to the web in real time.  We may see some very interesting apps in the next year or two, though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

