<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Caltrain Tweets &#187; Tutorial</title>
	<atom:link href="http://cow.org/c/archives/category/tutorial/feed" rel="self" type="application/rss+xml" />
	<link>http://cow.org/c</link>
	<description>Community supported Caltrain notices, one tweet at a time</description>
	<lastBuildDate>Tue, 11 May 2010 23:11:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Enough already</title>
		<link>http://cow.org/c/archives/113</link>
		<comments>http://cow.org/c/archives/113#comments</comments>
		<pubDate>Tue, 22 Sep 2009 06:42:19 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[@bikecar]]></category>
		<category><![CDATA[@caltrain]]></category>
		<category><![CDATA[Tutorial]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=113</guid>
		<description><![CDATA[When I created the service 3 years ago I tried to think of what I as a commuter (with or without a bicycle) would find useful in a tweet.  Talking with fellow riders I came up with the current Updating Guide because it seemed to just make sense.  Since the inception of the [...]]]></description>
			<content:encoded><![CDATA[<p>When I created the service 3 years ago I tried to think of what I as a commuter (with or without a bicycle) would find useful in a tweet.  Talking with fellow riders I came up with the current <a href="http://cow.org/c/updating-guide">Updating Guide</a> because it seemed to just make sense.  Since the inception of the service the nomenclature in the guide has worked without issue up until recently.</p>
<p>As you may know I don&#8217;t alter the content of tweets other than limit to a certain length to be able to append time stamps.  I believe that the community should be able to take my idea and initial set of guidelines and mold them to what really works.  It is with that belief I felt the service would evolve in a positive and useful way as Caltrain changed its service.  That is why I called them <em>guidelines</em>.  As it turned out everyone embraced them and felt they met the needs of the majority and as a result essentially became the rule more than a guide.</p>
<p>Recently the use of &#8216;bombardier&#8217; and &#8216;gallery&#8217; for car type and &#8216;limited&#8217; and &#8216;bbullet&#8217; for service type have been used with greater frequency to the frustration of many people.  This frustration has taken form in emails directly to me and to what amounts as a flame war on the public feed where hundreds of people follow.  Also it appears users have been editorializing, not consolidating multiple status in 1 tweet, and updating with no useful content.</p>
<p>It is because I received multiple direct emails from users saying, &#8220;decreasing the usefulness of the service&#8221;, &#8220;poor low signal to noise ratio&#8221;, and &#8220;tweets have taken over my twitter feed on a number of occasions [...] tweeting at length and uselessly about train type, sometimes with editorial comments, and doesn&#8217;t use the established conventions&#8221; that I realized I cannot take a complete laissez-faire attitude if I have any expectations of the service remaining useful.</p>
<p>It is because of this that I must now insist people adhere to the <a href="http://cow.org/c/updating-guide" target="_blank">Updating Guide</a> for updates.  The community has embraced my vision and has been very vocal about sticking with it.  Also the <a href="http://cow.org/c/updating-guide" target="_blank">Updating Guide</a> says at the very top,</p>
<blockquote><p>What makes an update useful or helpful? No matter what, updates need to be newsworthy and concise. If things are normal or how they should be there is no reason to announce it. Think of this service as a EAS for Caltrain. Too many updates could cause frustration or desensitize users who may stop following or updating which hurts everyone in the long run.</p></blockquote>
<p>I cannot help but to wonder why people insist on ignoring this fundamental belief.</p>
<p>One approach moving forward I had was replacing any instance of &#8216;bombardier&#8217; with &#8216;new&#8217; and &#8216;gallery&#8217; with &#8216;old&#8217; before sent to Twitter.  &#8216;Limited&#8217; and &#8216;bbullet&#8217; would also be removed because the service type is encoded in the route number itself.  As stated before:</p>
<p>1 = Local<br />
2 = Limited<br />
3 = Baby Bullet</p>
<p>In fact the direction (NB and SB) is also included &#8212; odd routes are Northbound and even routes are Southbound, but I am willing to allow the extra notation there.</p>
<p>But Ravi, you&#8217;re being hypocritical!</p>
<p>Yes, but this is why &#8212; I want the service to be easy for everyone.  It wasn&#8217;t until 3 years did I find out the direction and service encoding and it was because someone told me. I suspect I&#8217;m not alone.  Also I know countless people who outright refused to &#8220;ride the old trains.&#8221;  Not my words but theirs.  What is an old train here?  Yep, a gallery.  I didn&#8217;t make it up.  It is what it is.</p>
<p>So lets re-recap:</p>
<ol>
<li>Stick with the Updating Gude &#8212; drop the use of &#8216;bombardier&#8217;, &#8216;gallery&#8217;, &#8216;limited&#8217; and &#8216;bbullet&#8217; from the update.</li>
<li>Consolidate your tweets.</li>
<li>Keep your editorials to your blog or own Twitter feed. Some people subscribe to SMS updates of the feeds and some of those people pay for each SMS. Consider checking the feed for recent updates before you send one and ask yourself if it meets the criteria I set forth in the Updating Guide.</li>
</ol>
<p>I am saddened that I even had to write this post, but I am thrilled it took this long before I had to.  As hope everyone understands and realigns their updates with the Updating Guide and the requests of the community.  Posts will remain unedited (aside from length) and will remain for as long as people respect the service and others.</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/113/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Guides</title>
		<link>http://cow.org/c/archives/14</link>
		<comments>http://cow.org/c/archives/14#comments</comments>
		<pubDate>Fri, 08 Aug 2008 17:40:20 +0000</pubDate>
		<dc:creator>ravi</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Tutorial]]></category>

		<guid isPermaLink="false">http://cow.org/c/?p=14</guid>
		<description><![CDATA[Fritz over at Cycleicious wrote a blog post listing the steps to get setup with Twitter and using this service.  Inspired by this I adapted his guide and created one here.
It can be found at http://cow.org/c/getting-started (or http://cow.org/r/?3ce5 if the url must be short).
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.blogger.com/profile/04808661100114872654" target="_blank">Fritz</a> over at <a href="http://www.cyclelicio.us/" target="_blank">Cycleicious</a> wrote a <a href="http://www.cyclelicio.us/2008/08/caltrain-bike-car-updates-to-your.html" target="_blank">blog post</a> listing the steps to get setup with Twitter and using this service.  Inspired by this I adapted his guide and created one here.</p>
<p>It can be found at <a href="http://cow.org/c/getting-started" target="_blank">http://cow.org/c/getting-started</a> (or <a href="http://cow.org/r/?3ce5" target="_blank">http://cow.org/r/?3ce5</a> if the url must be short).</p>
]]></content:encoded>
			<wfw:commentRss>http://cow.org/c/archives/14/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
