Print Print

Tracking the Swarm

by Karoli on November 15, 2008

Back on the “track” bandwagon, folks, and this time in response to a series of discussions on Friendfeed and Identi.ca/Twitter about why it matters, and why tracking anything less than the full stream doesn’t work.

Brian Roy, who is working on a filtering tool for Friendfeed, wrote a post this morning claiming that “everything is myth“. My response: unicorns are mythical; track requires the full stream to be effective.

Start by looking at this. Note that the USGS official time for the China earthquake was 06:27:59.0. The first tweet came from scribeoflight, who I was not following (anyone in parenthesis is a track result and not from someone I follow) at the time at 10:35PM. Because GTalk doesn’t record seconds, it could have been as early as 10:35:01, or 6 minutes 2 seconds after the earthquake hit, reached scribeoflight, scribeoflightmessaged and it reached my IM. (note: time corrected — see comments.)

Every message that hit GTalk was sent by someone I didn’t follow. In the full transcript of that day, you can see that over time, I chose to follow those who were sending regular updates merely by sending twitter the command to follow them.

Another example:

Also in May, I tracked the term “tornado”, since they were hammering the Midwest. On May 22nd, messages started coming across about tornado warnings in Colorado, and messaged Amy Gahran, who I know lives in Boulder, to see if everything was all right, after receiving tracked messages indicating a tornado touchdown in Ft. Collins. Amy is a reporter, and while she was fine, she certainly had an interest in finding out what had happened and who was affected, since reports were also flooding in that a school had been damaged and one person killed. She wrote about our exchange here. What I found particularly compelling about her story was how difficult it was for her to get information in real time:

I went straight to the National Weather Service site — which is, I must say, a usability nightmare for someone seeking information about local severe weather in a hurry! I tried posting to Twitter links to specific NWS storm warnings, but apparently those pages are generated with session-specific URLs and so are useless if you send them as links to other Web users. (For future reference, it’s probably best to post links to NWS pages for state-specific current watches, warnings, and advisories — like this one for Colorado, so they can find the most up-to-date info for their part of the state.)

Next I jumped to the Ft. Collins Coloradoan site, where I found this report on the storm. That’s where I learned that the tornado actually touched down in Windsor, a town several miles southeast of Fort Collins (and much closer to the town of Greeley). Karoli sent me a links to video and photos of the large tornado, shot by a 9News team. I watched the video while looking out my window and noticing the sky above was growing darker. (UPDATE: Here’s more 9news video from during and after the tornado )

Here is the value of track, stated in 140 characters or less:

The ability to discover information, communicate, and act upon it across clouds in real-time whether mobile or stationary.

The notion of “limited track” is self-contradictory when seen in those terms. Track is not about ‘everything’, nor is it limited, nor does it guarantee “everything”. But what it does do is identify and follow the swarm around topics, people, events, or yes, disasters.

Speaking of disasters, there is a swarm around the word “Sylmar” right now. Looks like another wildfire has started, this time in Sylmar Hills. in the last five minutes, 35 messages have swarmed around that one term. It’s a bad fire, lots of wind, evacuations, and concern for the residents in that area. There’s a swarm around it, discovered through tracking the full stream, not my own Twitter stream. The value happens in the main stream, not my limited sphere of influence.

Photo Credit: Max Westby

Watch this space for the manifesto outlined on today’s NewsGang Live. Because Twitter needs to restore the ability to track, really track, in real time. Like we could back in May before they turned it off.

Twitter Track: Last seen 175 days, 11 hours, 22 minutes ago.

  • time correction: @scribeofflight 1st tweet at 02:35:33 EST
  • Thanks, I'll correct that in the post.
  • What? Unicorns? NOOOOO!!!! But I love unicorns :)
    It is amazing the nuances we will bring to ensure we disagree. And as I've said repeatedly over the past two days - I don't think we really disagree.
    The power of your anecdotes is obvious and compelling - and they are, in fact, powered by a scope of trackable data that is very large. But, as I've said on multiple occasions, I agree that the wider the scope of the trackable data the greater the potential value.
    My point isn't that less scope is good, it is that you can achieve value (discovery and participation in real time - mobile or otherwise) with a limited trackable scope. I don't suggest we should abandon the effort to have services/networks "open up" and share the full data.
    All I suggest is that we open up the track community to anyone working on solving the problem(s) of real time information discovery and participation. Make it inclusive - and not bear hug anyone who says - "hey we can do something here, even if we don't have the fire-hose".

    So we agree - but we don't. I'd love to be involved in the track community - but since I don't have a fire-hose of data to create solutions on... I guess I can't. I believe that my non-track limited information discovery and participation solutions will help the track community gain the leverage required to get the services to "open up". Hope that is enough.
  • Did Twitter ever explain why they turned off tracking?

    - Amy
  • Yes. They have said it's a scaling problem. It's really more about forming a business model around a very valuable stream of information, as they indicated in September at BearHug camp in an interview with Steve Gillmor.
  • @karoli said: "If you just send out self-promoting links and aren't interested in conversation when u follow, I not only won't follow, I will block."

    If one has access to the firehose, blocking is a myth. Twitter had many reasons for turning off the firehose. They had many reasons for turning off track.

    With new architecture & ToS, many reasons will be absent & your blocking will be enforced :)
  • Well, I disagree. When I tracked, I tracked users as well as terms. Was
    easy enough to choose to track users I wanted to read no matter what and
    scan the timeline when I felt like it for other things.

    So now I'm stuck having to follow back and block the idiots, something I
    never dealt with before.
  • you missed my point :)
  • No, I didn't :)
blog comments powered by Disqus

Previous post:

Next post: