I don’t listen to the radio (or watch TV or read newspapers much, frankly), so much thanks to John Bollwitt for passing along the news over to Twitter:
JohnBollwitt: Just heard @kenhardie say on @talk1410, 100+ twitter accounts coming to various #translink routes to follow for constant updates.
My first thought? Oh noes, fail whales! Twitter’s architecture has gotten much more robust in the past year, but over a hundred Twitter accounts? Even the MTA in New York has a mere total of 22 Twitter feeds, which are all listed at the 511Ny Twitter website.
There’s a couple of threads to my thinking here, so please bear with me. This first thread is about technical infrastructure. While I’m an enthusiastic user of both Twitter and Facebook, I think there’s a certain line to be drawn when it comes to using (or more accurately relying on) them, for functions that can easily be considered “mission critical applications.” We don’t have to look very far in the past to find instances where this can be disruptive. Not so long ago, Twitter made a controversial change to the way their users received @replies (now called mentions) to their timelines, so that I could no longer see messages mentioning people that I’m not following on Twitter. And let us not forget, that not that long ago, Twitter updates had been discontinued so that they weren’t being sent to cellphones in Canada!
Twitter’s model and community are amazing resources to take advantage of, but they’re more important to me as a proof of concept of the value of mobile and ubiquitous web applications. As I implied in my follow-up to John Bollwitt’s tweet, I think we need to ask some serious questions about whether we want our transit system’s information distribution and notification service reliant on a Silicon Valley-based startup with no readily discernible business plan. There are many smarter and more articulate people who can talk circles around me on how this is both or good bad, so I’m just going to advocate more thinking here.
There’s a second thread here, which is about TransLink’s use of Twitter more broadly. Make no mistake, I unequivocally think TransLink’s use of Twitter is an excellent, innovative and amazing thing. While Twitter is undoubtedly a huge part of our personal, and, increasingly, our professional lives, and I certainly think it’s important to go where the members of our community already are, I also fundamentally believe that the provision of the information that makes our transit system usable should not be contingent upon a rider or (Canadian) citizen’s registration with a third-party, American service.
That said, I think what I really want to ask is, is “what Twitter is for” inclusive of what TransLink wants to use it for? Is it for distributing information (yes)? Is it for sharing our thoughts in real-time with members of both our communities of interest (yes) and communities of location (yes)? How finely should we dice the feeds in order to ensure the technological resources to keep these services running are stable? Where do we cross the line from “nice to have” to “really f*&%ing important”?
If TransLink goes forward with this (which, really, I’m ready to admit I know next to nothing about at this point) I think the very least that TransLink needs to do is to be somewhat transparent about its relationship with Twitter. Are they working closely with Twitter to manage the traffic that may result? Could large amounts of traffic resulting from global Twitter usage (such as a large, social media noisy event like, oh, the Olympics or a hurricane) impact information being delivered to riders? Would our transit information service be vulnerable to DDoS attacks like the one that affected Twitter a couple weeks ago?
I would love to hear from the fellas at Handi Mobility (though they are down in SF right now), since I know they do a lot of thinking on mobile, its underlying infrastructure and end user experience, and have worked with TransLink on their SMS and mobile applications. I don’t think I’m freaking out unnecessarily, but I think it’s important to be wary of the centralization of all our short message information needs into a single application and Twitter particularly. It may save money for application developers like TransLink, and make managing feeds easy for end users, but it personally makes me a little queasy to think that a whole bunch of decisions that TransLink can make about the backend, would be made by Twitter on an ongoing basis.
Another event that speaks to this is the recent spam API incident on the TTCU_Community Twitter account (more info at TTCupdates.com). This account automatically re-tweets messages from Twitter with the hashtag #ttcu, and up until now it seems that the service has been used and maintained by community members without incident for allowing Toronto riders to share their observations about transit service. A couple days ago it all of sudden started sending out spam messages, which the developer is now looking into.
Logically, this is a scaling up of what the CMBCTransit account already does. While the prospect of getting a Twitter account for the #15 bus I ride everyday is exciting, I think I’d be much more interested in having TransLink maintain a separate service rather than relying on Twitter, which SFBART already does to some extent.
As you can see, I’m mostly asking questions in this post. If you have more questions, or any methods of answering the ones I’ve got, I’ve love to hear it in the comments and/or trackbacks.