<?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: OK, What the Real Phone Map Should Be</title>
	<atom:link href="http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php/feed" rel="self" type="application/rss+xml" />
	<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ok_what_the_real_phone_map_should_be</link>
	<description>Thoughts on the intersection of search, media, technology, and more.</description>
	<lastBuildDate>Tue, 21 May 2013 16:33:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Adam</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3447</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 07 Dec 2009 17:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3447</guid>
		<description>&lt;p&gt;Hey John, is this a step in the right direction for your phone map app idea?&lt;/p&gt;

&lt;p&gt;Mark the Spot: Tell AT&amp;T where the iPhone sucks&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.crunchgear.com/2009/12/07/mark-the-spot-tell-att-where-the-iphone-sucks/&quot; rel=&quot;nofollow&quot;&gt;http://www.crunchgear.com/2009/12/07/mark-the-spot-tell-att-where-the-iphone-sucks/&lt;/a&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hey John, is this a step in the right direction for your phone map app idea?</p>
<p>Mark the Spot: Tell AT&#038;T where the iPhone sucks</p>
<p><a href="http://www.crunchgear.com/2009/12/07/mark-the-spot-tell-att-where-the-iphone-sucks/" rel="nofollow">http://www.crunchgear.com/2009/12/07/mark-the-spot-tell-att-where-the-iphone-sucks/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bertil</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3446</link>
		<dc:creator>Bertil</dc:creator>
		<pubDate>Mon, 30 Nov 2009 00:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3446</guid>
		<description>&lt;p&gt;Actually, operators already do that: that&#039;s the main reason they monitor call logs (that and the fact that they are all Visitors, bound to erase humanit…) It&#039;s much easier for them to have their engineers do it, although it doesn&#039;t convey the added frustration from being a disconnected geek. Such an app would probably be far more useful by channelling anger (an important aspect) rather than signalling issues.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Actually, operators already do that: that&#8217;s the main reason they monitor call logs (that and the fact that they are all Visitors, bound to erase humanit…) It&#8217;s much easier for them to have their engineers do it, although it doesn&#8217;t convey the added frustration from being a disconnected geek. Such an app would probably be far more useful by channelling anger (an important aspect) rather than signalling issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daina Middleton</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3445</link>
		<dc:creator>Daina Middleton</dc:creator>
		<pubDate>Thu, 12 Nov 2009 13:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3445</guid>
		<description>&lt;p&gt;We hear you now!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>We hear you now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sikiş izle</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3444</link>
		<dc:creator>Sikiş izle</dc:creator>
		<pubDate>Thu, 05 Nov 2009 01:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3444</guid>
		<description>&lt;p&gt;3G technology has come to be very popular since. I think the GPS system is quite useful, especially when traveling by car instead of unknown points from mobile phones to ask to see our work.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>3G technology has come to be very popular since. I think the GPS system is quite useful, especially when traveling by car instead of unknown points from mobile phones to ask to see our work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3443</link>
		<dc:creator>Timothy</dc:creator>
		<pubDate>Wed, 04 Nov 2009 00:33:20 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3443</guid>
		<description>&lt;p&gt;While a slightly different angle than where you took the concept, CNET and Root Wireless have teamed up to tackle this problem with an approach like what is mentioned in the comments.&lt;/p&gt;

&lt;p&gt;You can find the details here: &lt;a href=&quot;http://news.cnet.com/8301-30677_3-10368459-244.html&quot; rel=&quot;nofollow&quot;&gt;http://news.cnet.com/8301-30677_3-10368459-244.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As you can imagine, crowdsourcing this data at the intersection of handset, carrier, and usage when there is data or voice failure could finally make this a transparent communication void of any marketers agenda.&lt;/p&gt;

&lt;p&gt;(full disclosure - I do work for CNET)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>While a slightly different angle than where you took the concept, CNET and Root Wireless have teamed up to tackle this problem with an approach like what is mentioned in the comments.</p>
<p>You can find the details here: <a href="http://news.cnet.com/8301-30677_3-10368459-244.html" rel="nofollow">http://news.cnet.com/8301-30677_3-10368459-244.html</a></p>
<p>As you can imagine, crowdsourcing this data at the intersection of handset, carrier, and usage when there is data or voice failure could finally make this a transparent communication void of any marketers agenda.</p>
<p>(full disclosure &#8211; I do work for CNET)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3442</link>
		<dc:creator>Timothy</dc:creator>
		<pubDate>Wed, 04 Nov 2009 00:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3442</guid>
		<description>&lt;p&gt;While a slightly different angle than where you took the concept, CNET and Root Wireless have teamed up to tackle this problem with an approach like what is mentioned in the comments.&lt;/p&gt;

&lt;p&gt;You can find the details here: &lt;a href=&quot;http://news.cnet.com/8301-30677_3-10368459-244.html&quot; rel=&quot;nofollow&quot;&gt;http://news.cnet.com/8301-30677_3-10368459-244.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As you can imagine, crowdsourcing this data at the intersection of handset, carrier, and usage when there is data or voice failure could finally make this a transparent communication void of any marketers agenda.&lt;/p&gt;

&lt;p&gt;(full disclosure - I do work for CNET)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>While a slightly different angle than where you took the concept, CNET and Root Wireless have teamed up to tackle this problem with an approach like what is mentioned in the comments.</p>
<p>You can find the details here: <a href="http://news.cnet.com/8301-30677_3-10368459-244.html" rel="nofollow">http://news.cnet.com/8301-30677_3-10368459-244.html</a></p>
<p>As you can imagine, crowdsourcing this data at the intersection of handset, carrier, and usage when there is data or voice failure could finally make this a transparent communication void of any marketers agenda.</p>
<p>(full disclosure &#8211; I do work for CNET)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3441</link>
		<dc:creator>Timothy</dc:creator>
		<pubDate>Wed, 04 Nov 2009 00:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3441</guid>
		<description>&lt;p&gt;While a slightly different angle than where you took the concept, CNET and Root Wireless have teamed up to tackle this problem with an approach like what is mentioned in the comments.&lt;/p&gt;

&lt;p&gt;You can find the details here: &lt;a href=&quot;http://news.cnet.com/8301-30677_3-10368459-244.html&quot; rel=&quot;nofollow&quot;&gt;http://news.cnet.com/8301-30677_3-10368459-244.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As you can imagine, crowdsourcing this data at the intersection of handset, carrier, and usage when there is data or voice failure could finally make this a transparent communication void of any marketers agenda.&lt;/p&gt;

&lt;p&gt;(full disclosure - I do work for CNET)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>While a slightly different angle than where you took the concept, CNET and Root Wireless have teamed up to tackle this problem with an approach like what is mentioned in the comments.</p>
<p>You can find the details here: <a href="http://news.cnet.com/8301-30677_3-10368459-244.html" rel="nofollow">http://news.cnet.com/8301-30677_3-10368459-244.html</a></p>
<p>As you can imagine, crowdsourcing this data at the intersection of handset, carrier, and usage when there is data or voice failure could finally make this a transparent communication void of any marketers agenda.</p>
<p>(full disclosure &#8211; I do work for CNET)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3440</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Tue, 03 Nov 2009 23:38:56 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3440</guid>
		<description>&lt;p&gt;Sounds like a great idea.&lt;/p&gt;

&lt;p&gt;Would it be possible to automate on smartphones by having an &#039;ap&#039; running that noted your co-ords when signal drops and automatically popped the pin in for you?&lt;/p&gt;

&lt;p&gt;It&#039;d have to be dynamic so only putting one in if signal was lost for an extended time else basements and such would all have low signal.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Sounds like a great idea.</p>
<p>Would it be possible to automate on smartphones by having an &#8216;ap&#8217; running that noted your co-ords when signal drops and automatically popped the pin in for you?</p>
<p>It&#8217;d have to be dynamic so only putting one in if signal was lost for an extended time else basements and such would all have low signal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Hawkinson</title>
		<link>http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3439</link>
		<dc:creator>Alex Hawkinson</dc:creator>
		<pubDate>Tue, 03 Nov 2009 23:23:09 +0000</pubDate>
		<guid isPermaLink="false">http://battellemedia.com/archives/2009/11/ok_what_the_real_phone_map_should_be.php#comment-3439</guid>
		<description>&lt;p&gt;This is a ~great~ idea and could open up a lot of transparency.  We have a bunch of carriers that we are very close to and I intend to pass your suggestion along.&lt;/p&gt;

&lt;p&gt;Alternatively, it could be done in a way that is independent of any specific carrier, but would be useful to have marketing muscle behind it to get enough visibility for critical mass.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>This is a ~great~ idea and could open up a lot of transparency.  We have a bunch of carriers that we are very close to and I intend to pass your suggestion along.</p>
<p>Alternatively, it could be done in a way that is independent of any specific carrier, but would be useful to have marketing muscle behind it to get enough visibility for critical mass.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
