It’s been many months since I found out about TTYtter, a command line Twitter client written in Perl. Though some users might bemoan the lack of a snazzy graphical interface, it is that very lack which appeals to me. TTYtter places only a very tiny load on system resources, which means my Twitter addiction won’t get in the way of running VMs to test various configurations and procedures. Being command-line based, I can run it in a screen session which means that I can resume my Twittering from wherever I happen to be and not have to re-configure my client.
I don’t claim to be a TTYtter expert, but I thought I’d share my own configuration for other newbs. TTYtter looks in $HOME/.ttytterrc by default, and here’s my default configuration:
#Check to see if I'm running the current version vcheck=1 # What hash tags do I care about? track='#Purdue #OSMacTalk #MarioMarathon' # Colors, etc are good! ansi=1 # I'm dumb. Prompt me before a tweet posts verify=1 # Use some readline magic readline=1 # Check for mentions from people I don't follow mentions=1
Of course, there are certain times that the default configuration isn’t what I want. When I was reading tweets in rapid-fire succession during the Mario Marathon, I didn’t want non-Mario tweets to get in the way, so I used a separate configuration file:
# Don't log in and burn up my rate limit anonymous=1 # Find tweets related to the marathon track=#MarioMarathon "Mario Marathon" # Don't show my normal timeline notimeline=1 # Colors, etc are awesome! ansi=1 # Only update when I say so. This keeps the tweet I'm in the middle of reading # from being scrolled right off my screen synch
There are a lot of other ways that TTYtter can be used, and I’m sure @doctorlinguist will tell me all of the ways I’m doing things wrong, but if you’re in the market for a new, multi-platform Twitter client, you should give this one a try.
Pingback: mmtter: a front end for TTYtter « Blog Fiasco