<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Idea #3: Dropped Call Registry</title>
	<atom:link href="http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/</link>
	<description>the journey is the reward</description>
	<lastBuildDate>Thu, 10 Nov 2011 11:52:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Adam Seever</title>
		<link>http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/#comment-445</link>
		<dc:creator><![CDATA[Adam Seever]]></dc:creator>
		<pubDate>Tue, 31 Aug 2010 17:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damonc.com/?p=186#comment-445</guid>
		<description><![CDATA[Interesting idea. Carriers maintain their own (very detailed) data on calls that actually get dropped, but that data won&#039;t become public, and also doesn&#039;t account for calls that couldn&#039;t be made because of a lack of signal. So something that reported dead zones would be useful for both carriers and the public, and dropped call info would be useful to the public. 

+1 on the idea of something that isn&#039;t self-reported because of potential abuse, but agreed that it is paradoxical for reporting network outtages. 

This could be useful if you were trying to determine which carrier to go with based on where you live, whether your cell phone would work at the apartment you&#039;re looking at, and the more general &quot;is it down for everyone or just me&quot; for a particular location.]]></description>
		<content:encoded><![CDATA[<p>Interesting idea. Carriers maintain their own (very detailed) data on calls that actually get dropped, but that data won&#8217;t become public, and also doesn&#8217;t account for calls that couldn&#8217;t be made because of a lack of signal. So something that reported dead zones would be useful for both carriers and the public, and dropped call info would be useful to the public. </p>
<p>+1 on the idea of something that isn&#8217;t self-reported because of potential abuse, but agreed that it is paradoxical for reporting network outtages. </p>
<p>This could be useful if you were trying to determine which carrier to go with based on where you live, whether your cell phone would work at the apartment you&#8217;re looking at, and the more general &#8220;is it down for everyone or just me&#8221; for a particular location.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: damonclinkscales</title>
		<link>http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/#comment-26</link>
		<dc:creator><![CDATA[damonclinkscales]]></dc:creator>
		<pubDate>Tue, 02 Mar 2010 01:04:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damonc.com/?p=186#comment-26</guid>
		<description><![CDATA[I&#039;m glad the Mark the Spot app is there.  I guess it doesn&#039;t work too well if the network is having problems, but it has the benefit of *not* being self-reported (which is subject to abuse).   What I am thinking of here is something that&#039;s cross-carrier and public, which no telecom company will ever provide.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m glad the Mark the Spot app is there.  I guess it doesn&#8217;t work too well if the network is having problems, but it has the benefit of *not* being self-reported (which is subject to abuse).   What I am thinking of here is something that&#8217;s cross-carrier and public, which no telecom company will ever provide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willie Abrams</title>
		<link>http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/#comment-25</link>
		<dc:creator><![CDATA[Willie Abrams]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 18:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damonc.com/?p=186#comment-25</guid>
		<description><![CDATA[I use the AT&amp;T mark the spot app, too.]]></description>
		<content:encoded><![CDATA[<p>I use the AT&amp;T mark the spot app, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Treadaway</title>
		<link>http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/#comment-12</link>
		<dc:creator><![CDATA[Chris Treadaway]]></dc:creator>
		<pubDate>Tue, 29 Dec 2009 07:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damonc.com/?p=186#comment-12</guid>
		<description><![CDATA[I really think this is cool -- kind of like a BSOD log file for Windows but treating a dropped call on a cell phone like the crash.

I&#039;d add details on the hardware &amp; firmware version... but that&#039;s about my only nit.  All told that information should be easy to capture and send to a server upon next data or wireless network connection.

CHris]]></description>
		<content:encoded><![CDATA[<p>I really think this is cool &#8212; kind of like a BSOD log file for Windows but treating a dropped call on a cell phone like the crash.</p>
<p>I&#8217;d add details on the hardware &amp; firmware version&#8230; but that&#8217;s about my only nit.  All told that information should be easy to capture and send to a server upon next data or wireless network connection.</p>
<p>CHris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maczter</title>
		<link>http://blog.damonc.com/2009/12/29/idea-3-dropped-call-registry/#comment-10</link>
		<dc:creator><![CDATA[maczter]]></dc:creator>
		<pubDate>Tue, 29 Dec 2009 06:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damonc.com/?p=186#comment-10</guid>
		<description><![CDATA[Hmm...

AT&amp;T is doing this with the &quot;Mark The Spot&quot; app released a couple of weeks ago.

More info here:

http://appshopper.com/utilities/att-mark-the-spot

http://gizmodo.com/5420524/mark-the-spot-iphone-app-tells-att-where-they-suck

While a lot of people initially say &quot;how can I report a spot with no service if I have no service, you can do it as long as you&#039;re willing to fire up the app so it can grab your location, then fill in the info and move or travel to somewhere where you actually do have service. :)]]></description>
		<content:encoded><![CDATA[<p>Hmm&#8230;</p>
<p>AT&amp;T is doing this with the &#8220;Mark The Spot&#8221; app released a couple of weeks ago.</p>
<p>More info here:</p>
<p><a href="http://appshopper.com/utilities/att-mark-the-spot" rel="nofollow">http://appshopper.com/utilities/att-mark-the-spot</a></p>
<p><a href="http://gizmodo.com/5420524/mark-the-spot-iphone-app-tells-att-where-they-suck" rel="nofollow">http://gizmodo.com/5420524/mark-the-spot-iphone-app-tells-att-where-they-suck</a></p>
<p>While a lot of people initially say &#8220;how can I report a spot with no service if I have no service, you can do it as long as you&#8217;re willing to fire up the app so it can grab your location, then fill in the info and move or travel to somewhere where you actually do have service. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

