#clouds: Using Twitter as a Command Line Service
January 9, 2008
You may have noticed Hash Tags appear on Twitter recently, promoted by Chris from Citizen Agency. You need to read this post and this one too, to follow this idea. Oh, and have a look at the Twitter Wiki HashTag page for a comprehensive oveview.
HashTags are a way to tag Tweets so that Followers can keep track of a story/theme/place/activity. Like a Channel or a Group.
I think they are missing the affordance values of Twitter. (OoOooOooooh, can I really say Twitter should NOT be used for something?)
HashTags are an inline denotation of meaning within the Tweet; I think this is self referential and perhaps there is a better way of using the system for tracking activities that followers want to relate to.
As with Social Objects, a story/theme/place/activity can be defined as a Class – an object that contains actions, or Methods. By trying to turn a single Tweet into an object, defies the value in using Tweets as Methods – Considering Twitters call to action “What are you doing?” the 140char space is perfect for Methods, not Objects.
Now, there are various Twitter aggregators around – HashTag.org being the most relevent to this situation. Snitter (which I use and love) also allows HashTag aggregation. This is fine, I can gather all the the relevant posts according to a HashTag instantly.
But, here’s the rub, Twitter’s within the range of a HashTag subject bring value and are excluded from the aggregation. Twitter Vision style aggregation can help see within a geographical aggregation, but for broader value aggregation, and by the way that language works, there is not an ontology that can scale to capture a deep rich picture of the subject.
Unless we use Twitter as a Command Line to activate 3rd party services to produce a Media Cloud. A Media cloud is a semantically collected set of web services based around a story/theme/place/activity. Like Where are the Joneses?
Ordinarily, a user has to go to all these web services, set up an account and then link them all together. I propose this can all be done via Twitter through a recognisable command, which I’m calling a Twoot (ref: W00t). Here’s a rough UML Activity Diagram to explain how this could work.
Now, there’s an upcoming suite of API enabling concepts rising up that can really pull this together. OAUTH, Open ID and Microformats (Now on Twitter)are all useful for transferring, connecting and evolving the Media Cloud, not to mention the blogosphere grokking via Technorati, Friendfeed and of course Google and it’s merry band of services. AMPL is really close to this too.
Social Nets are also handy, why cant FaceBook applications be libraries ready for deployment upon a Twitter Command (a Twoot), thus attaching the HashCloud to the daily FB addictions. OpenSocial – very handy for attaching the broad range of webservices. I think Ning could be a major service in this operation. Flickr would be essential.
Depending on the string sent from Twitter, the array of services can be controlled – look at the range of webservices as an à la carte menu. A set of parameters could be sent requesting which services, or providers, require activation.
Now all this could be the start of spam hell, what would be stopping anyone setting up Media Clouds through a HashCloud command? Equally, think of the number of Brands establishing Media Clouds for any eventuality. Splogs are bad enough but Google does a tidy job of keeping them out of searches.
But an active MediaCloud would be judged by the vortex it would create around the story/theme/place/activity. The MediaCloud would transform to a MediaVortex if there was genuine activity, SpamClouds would just float away, dissolve, vanish. A MediaVortex would root itself at the focus of attention.