Why I've put a Twitter client on my smartphone
I recently got a smartphone, and one of the things I put on it is a Twitter client. In fact I went out of my way to pay money for a good one (and it was totally worth it; Tweetbot has a much better interface than the free official Twitter client, especially if you use multiple accounts). Given that I've said I need to break my Twitter addiction, this may seem like an odd move, but there's a method to my madness and it's worked out pretty well so far.
One of the things my phone is for is entertainment, or more specifically killing time if I have nothing else to do. If I'm waiting somewhere or stuck somewhere, I can pull out my phone and do something. Twitter is an excellent source of time-killing entertainment; if you follow enough people there's almost always some new activity to read and look at. Tweetbot dials this up to full power by making it fluid and easy to scroll through tweets, skimming them and dipping into bits, and it will normally even feed in a continual stream of updates. The Tweetbot interface is great for quickly dipping in and skimming around and being temporarily absorbed.
(Since I'm never going to read everything on the phone, it also makes it easier to check in briefly just to skim the latest conversations. This makes it surprisingly similar to my social MUD experience; I can drop in, see the current chatter, and if I want I can go back a bit to get the context.)
So is using Twitter from my phone a lot a tempting thing? Actually no. First, my phone is clearly not good if I want to be actively engaged with Twitter because of the limitations of its interface. Reading web pages that people link to is not a great experience simply due to limited size, it's not a good environment for multi-tasking (where I may start looking at a web page, read a bit, and then put it aside for later), and I'm probably never going to be fluid enough at phone typing to make conversations and so on something I want to do on the phone. If and when I actively care about Twitter, I want to be interacting with it through my desktop and my client there.
Second, using Twitter from my phone means that I can't possibly fool myself and believe that I'm multi-tasking effectively and checking into Twitter 'just a little bit' in between other things. The phone itself is a single-tasking environment, and using Twitter (or anything else) on it means that all my attention is on my phone, not on my computer. I can't pretend that picking up my phone is anything other than consciously ignoring what I'm doing on the computer. This isn't a casual distraction that snowballs, it's a deliberate shift and that makes it much less likely to happen.
Although it's still the early days, I think I've finally managed to make a real shift in how I deal with Twitter, one that simultaneously sees me giving it less attention while in some ways following it better (because I can and do dip in to current conversations periodically).
The MyDoom worm is still out there
One of the interesting things that happens when you start paying attention to attachment types and tracking detected malware is that, well, you stumble over some things you didn't expect. So there I was, looking at our listing of recently rejected malware, when I saw:
[...] rejected 1bqFNH-0008Cv-8D from firstname.lastname@example.org to <redacted>: identified virus: W32/MyDoom-O
MyDoom is infamous, but it's also old; it dates from 2004. It's now more than ten years later and some computers are still sending MyDoom variants around to people. This is both an impressive testimony to the tenaciousness of certain sorts of things and a depressing sign of how slow security updates are to propagate around. Since we've been sent multiple MyDoom messages since we started logging these, there are clearly still a decent number of infected machines out there spewing malware spam out into the world.
This particular example is probably authentically old, as it was
trying to mail a
.scr file that wasn't even inside a ZIP archive.
Other variants we've seen have mailed
.bats inside ZIPs, or
.coms, or a few other extremely obvious bad file types that almost
no one allows through any more. In fact MyDoom is responsible for
us going out of our way to explicitly reject a few 'no one would
be crazy enough to send this, especially outside a ZIP file' file
types. Perhaps this is overkill but who knows, perhaps someday there
will be another mutation that our commercial anti-spam system doesn't
(That this was detected as malware instead of being rejected for file
types does mean that yes, we weren't rejecting
.scr file attachments.
Probably I should fix that. Sadly this kind of work can be a never
ending whack-a-mole saga as you just find more and more bad file types
to block. I would kind of like to stop paying attention to this at some
point, but the usual problem is in effect
here; having created logs, I feel a compulsion to look at them.)