<?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"
	>
<channel>
	<title>Comments on: Subway Status App on Facebook</title>
	<atom:link href="http://blog.andrewparker.net/2007/08/18/subway-status/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.andrewparker.net/2007/08/18/subway-status/</link>
	<description>Tech, Entrepreneurship, and Venture Capital in New York City</description>
	<pubDate>Wed, 19 Nov 2008 04:05:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: michael galpert</title>
		<link>http://blog.andrewparker.net/2007/08/18/subway-status/#comment-74170</link>
		<dc:creator>michael galpert</dc:creator>
		<pubDate>Sun, 19 Aug 2007 18:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andrewparker.net/2007/08/18/subway-status/#comment-74170</guid>
		<description>the mta should create a twitter mashup for each subway line that would enable ppl to subscribe to mta info as well as have ppl twitter information. With texting ppl can type the message and have it be sent once they have service again.

i would have loved to have had something like this when there was the mta meltdown weeks ago</description>
		<content:encoded><![CDATA[<p>the mta should create a twitter mashup for each subway line that would enable ppl to subscribe to mta info as well as have ppl twitter information. With texting ppl can type the message and have it be sent once they have service again.</p>
<p>i would have loved to have had something like this when there was the mta meltdown weeks ago</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Marman</title>
		<link>http://blog.andrewparker.net/2007/08/18/subway-status/#comment-74136</link>
		<dc:creator>Tim Marman</dc:creator>
		<pubDate>Sun, 19 Aug 2007 15:32:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andrewparker.net/2007/08/18/subway-status/#comment-74136</guid>
		<description>The other issue they have with crowdsourcing is that the point where you would be most likely to write about the delay is when you're on the platform... where there's most likely no phone service. Even if you remember to do it when you get out of the subway, it will probably be too late anyway.

And yeah, I would definitely not be too keen on meeting up with Homeless Tom :)</description>
		<content:encoded><![CDATA[<p>The other issue they have with crowdsourcing is that the point where you would be most likely to write about the delay is when you&#8217;re on the platform&#8230; where there&#8217;s most likely no phone service. Even if you remember to do it when you get out of the subway, it will probably be too late anyway.</p>
<p>And yeah, I would definitely not be too keen on meeting up with Homeless Tom :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Marman</title>
		<link>http://blog.andrewparker.net/2007/08/18/subway-status/#comment-74135</link>
		<dc:creator>Tim Marman</dc:creator>
		<pubDate>Sun, 19 Aug 2007 15:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andrewparker.net/2007/08/18/subway-status/#comment-74135</guid>
		<description>The other issue they have with crowdsourcing is that the point where you would be most likely to write about the delay is when you're on the platform... where there's most likely no phone service. Even if you remember to do it when you get out of the subway, it will probably be too late anyway.

And yeah, I would definitely not be too keen on meet up with Homeless Tom :)</description>
		<content:encoded><![CDATA[<p>The other issue they have with crowdsourcing is that the point where you would be most likely to write about the delay is when you&#8217;re on the platform&#8230; where there&#8217;s most likely no phone service. Even if you remember to do it when you get out of the subway, it will probably be too late anyway.</p>
<p>And yeah, I would definitely not be too keen on meet up with Homeless Tom :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.509 seconds -->
