CorridorCommute Blog

Updates on the CorridorCommute.com website

Announcing CorridorSpeed

without comments

This morning, I’d like to introduce CorridorSpeed, a derivative of CorridorCommute.  CorridorSpeed is a special feed with updates specifically tailored with information about speed traps and automated ticketing areas.  Like CorridorCommute, all content is created by users in Cedar Rapids, Iowa City, and surrounding communities.

CorridorSpeed is available today on Twitter, and will soon also be available at speed.corridorcommute.com.  Support will also be included in the recently announced iPhone app.

Over the past year, CorridorCommute.com and its Twitter feed have seen great growth in followers and popularity.  It has been exciting to see how the community has embraced the service, and how local media groups have helped expand its audience.  While observing how the community has shaped the service, it became clear there was a special need for speed-related news and updates.  These updates are similar to others found on CorridorCommute, but may be more frequent and target different audiences, which made creating CorridorSpeed a logical next step.

Contribution (#csu)

Today, all current CorridorCommute contributors are also contributors on CorridorSpeed. Similar to how CorridorCommute uses a magic hashtag (#ccu) for flagging tweets as for-CorridorCommute, CorridorSpeed employs a similar mechanism.  Users who would like a tweet to be captured by CorridorSpeed should include #csu (“CorridorSpeed Update”) at the end of the message.  For more details on how the hashtag capture process works, please check out this blog post.

If you’d like to start contributing to CorridorSpeed, please  send an email to corridorcommute -at- gmail -dot- com.  Currently, contributions are only possible through Twitter, so please include your Twitter username.

As always, I’d appreciate any and all feedback.  Please send questions / comments to the previously mentioned email address.

Written by Thaddeus

August 9th, 2010 at 11:18 pm

Posted in Uncategorized