<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Bostonist: How Are Those T Alerts Working Out for Ya?</title>
<link>http://bostonist.com/2007/12/03/how_are_those_t.php</link>
<description>All comments for How Are Those T Alerts Working Out for Ya?</description>
<language>en-us</language>
<copyright>2009 rickbang</copyright>
<lastBuildDate>Mon, 05 Jan 2009 16:29:29 -0500</lastBuildDate>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<managingEditor>rick@bostonist.com</managingEditor>
<webMaster>rick@bostonist.com</webMaster>
<ttl>60</ttl>
<item>
<title>akwhitacre</title>
<link>http://bostonist.com/2007/12/03/how_are_those_t.php#comment-1244403</link>
<guid isPermaLink="true">http://bostonist.com/2007/12/03/how_are_those_t.php#comment-1244403</guid>
<category>Comments</category>
<pubDate>Mon, 03 Dec 2007 15:37:41 -0500</pubDate>
<description>&lt;p&gt;I&apos;ll give you another reason the alerts aren&apos;t helpful (at least the text message ones): you can&apos;t specify a narrow enough time period to receive them. The only period relevant to most morning commutes would be the option &quot;AM Peak 5:00 AM - 9:30 AM&quot;, but if people leave for work around, say, 8:00-8:30am, why would they want text messages waking them up at 5:00am, 6:00am, etc.? Would it really be that hard to let people specify a time? Something like that really would have helped me this morning when my regular bus was 20 minutes late due to a breakdown of an earlier bus--I&apos;d rather get one message about the 8:20 bus than five messages about the five buses affected before it.&lt;/p&gt;</description>
</item>
</channel>
</rss>
