<?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: Taking a look at Twttr.com</title>
	<atom:link href="http://www.mobileindustryreview.com/2006/07/taking_a_look_a.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mobileindustryreview.com/2006/07/taking_a_look_a.html</link>
	<description>Daily news and opinion for 250,000 industry executives and mobile fanatics</description>
	<lastBuildDate>Tue, 14 Feb 2012 22:14:00 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan Lane</title>
		<link>http://www.mobileindustryreview.com/2006/07/taking_a_look_a.html/comment-page-1#comment-257</link>
		<dc:creator>Dan Lane</dc:creator>
		<pubDate>Sun, 16 Jul 2006 21:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.co.uk/2006/07/taking_a_look_at_twttrcom.html#comment-257</guid>
		<description>Ewan: when I first saw twttr I knew it&#039;d never work in the UK because:

1. In the UK, everyone would call it twatter. I read it as twatter even after I tried to condition myself to read it as twitter (although my fragile mind has been warped from working with pornographers). This is not a good thing from a marketing point of view (or maybe it is!)

2. Like you pointed out it requires the user to stop what they are doing and update twttr, ergo, every user&#039;s status will be &quot;Updating twttr&quot;.

It&#039;d be much better to use one of the similar services (I&#039;m assuming these exist, if they don&#039;t then it&#039;s my idea and you can&#039;t have it!) that runs an app to check the Cell ID and figure out where you are (based on a user-updated database). It won&#039;t say &quot;I&#039;m in Pizza Express&quot; but it will say &quot;I&#039;m in London&quot;, &quot;I&#039;m in Essex&quot; or &quot;I&#039;m in North Wales&quot; at which point I can say, hey Ewan is nearby, I&#039;ll ping him and see if he fancies a pint.

Jack: as far as I know sending a text messages to that international long-number would incur a higher-than-usual cost for most users. To make twttr appealing to UK users you could look into getting a UK long number (not a shortcode, no networks include shortcodes in their inclusive text plans).
</description>
		<content:encoded><![CDATA[<p>Ewan: when I first saw twttr I knew it&#8217;d never work in the UK because:</p>
<p>1. In the UK, everyone would call it twatter. I read it as twatter even after I tried to condition myself to read it as twitter (although my fragile mind has been warped from working with pornographers). This is not a good thing from a marketing point of view (or maybe it is!)</p>
<p>2. Like you pointed out it requires the user to stop what they are doing and update twttr, ergo, every user&#8217;s status will be &#8220;Updating twttr&#8221;.</p>
<p>It&#8217;d be much better to use one of the similar services (I&#8217;m assuming these exist, if they don&#8217;t then it&#8217;s my idea and you can&#8217;t have it!) that runs an app to check the Cell ID and figure out where you are (based on a user-updated database). It won&#8217;t say &#8220;I&#8217;m in Pizza Express&#8221; but it will say &#8220;I&#8217;m in London&#8221;, &#8220;I&#8217;m in Essex&#8221; or &#8220;I&#8217;m in North Wales&#8221; at which point I can say, hey Ewan is nearby, I&#8217;ll ping him and see if he fancies a pint.</p>
<p>Jack: as far as I know sending a text messages to that international long-number would incur a higher-than-usual cost for most users. To make twttr appealing to UK users you could look into getting a UK long number (not a shortcode, no networks include shortcodes in their inclusive text plans).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jack</title>
		<link>http://www.mobileindustryreview.com/2006/07/taking_a_look_a.html/comment-page-1#comment-256</link>
		<dc:creator>jack</dc:creator>
		<pubDate>Sun, 16 Jul 2006 17:08:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.co.uk/2006/07/taking_a_look_at_twttrcom.html#comment-256</guid>
		<description>Hello Ewan,

Twttr works in the UK with our long-code: 415-283-8611.  We&#039;ve had some problems with the gateway software over the past 24h which has prevented sending out passwords properly.  This should be resolved shortly.

We are looking to be a global service (one of our developers lives in Germany). Thank you for trying it out!

jack (from twttr)</description>
		<content:encoded><![CDATA[<p>Hello Ewan,</p>
<p>Twttr works in the UK with our long-code: 415-283-8611.  We&#8217;ve had some problems with the gateway software over the past 24h which has prevented sending out passwords properly.  This should be resolved shortly.</p>
<p>We are looking to be a global service (one of our developers lives in Germany). Thank you for trying it out!</p>
<p>jack (from twttr)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

