Next Twitter Client

What I’m looking for in my next Twitter Client:

  • Ability to edit the sound for audio notification of new tweets. I want to make it distinguishable, unobtrusive, and not so ‘clever’.
  • Growl (or similar) notification. Again, the goal here it to be unobtrusive, but still give me a quick passive peek into what’s going on.
  • Allow me to create regexp filters. There are many times, when I want to simply filter out a sub-conversation I don’t want taking up mental bandwidth. It makes it harder to look through the trees. Generally, these will have short shelf-life. But there are a few that I would keep on all the time. i.e. “good morn.*” or “hello new.*” are not tweets I need to see.
  • Add a new sub-section for tweets beginning with @. Most twitter clients are great about having a special ‘place’ for direct messages and replies. Some hide them on their own page, others color the messages different in-line. I also want a simple way to toggle between viewing tweets which begin with ‘@’ so I can primarily see people’s original thoughts, and then choose to view ‘the conversation.’

What do you want from a twitter client?

  • What comes to mind in the moment is something that would act like a bin for interesting items; not the tweets themselves (though “faves” can be a fun thing to do) but the referent.
    What I’m doing right now, under the guise of being kind and generous *snort* is repeating the item having SnipUrl’d it into my own collection and passing that on to those I follow … which, I suspect, in most cases just makes it redundant.

    cheers

  • What would that look like in a client? A del.icio.us button beside every link?

  • In TwitBin sidebar there’s a teenie [W] beside the teenie [@], so that look. What I can’t grasp (yet?) is function.
    Perhaps target is config option, delic or technorati or google b’marks or whatevuh … long list!
    What brought it to mind … no, check that … what caused me to blurt an as.yet incomplete thought was heh I happened to be reading ontology/taxonomy/documentation for testing … what a datum “means” depends on context.
    If you pass me a URL it means Xsub1 … if from DWiner, then Xsub2, know what I mean?
    So I’m really talking about stashing context-rich … preserving the cookie crumbs … the makings of a graphable XFN-like artifact compendium?

    (blue-sky mode here … it’s Sunday! *grin*)