I used to get annoyed when someone would send a complete screen shot along with their tech support request. I thought it was a waste of bandwidth when a simple text message would do just as well, and be faster to send, receive and display.

But the thing is, screenshots have their advantages. For one thing, they’re exact. There’s no risk of an error code being mistyped.

More importantly, a screenshot can tell you other information that the user hasn’t thought to mention. This is critical, because the reason people call tech support is because they don’t know how to solve a particular problem…and that often means they don’t know which information is relevant.

Like, say, the fact that they’re running another program which happens to conflict with the one that they’re calling about.

Still, I wish Windows would create a file instead of copying the screen to the clipboard. Users need to paste it into something, so they paste it into what they’re most familiar with: Microsoft Word — something even less suited for sending images by email than a .BMP file created by Paint.

Comic-Con International is rapidly approaching, and you know what that means: it means I’m thinking about mobile computing again!

Right now, I’ve got a G1 Android-based phone, and Katie and I share a MacBook. The G1 is showing its age, and it would be nice to have a second computer to do things like manage photos with while traveling.

So. Options.

1. Upgrade the phone. I’d like to stick with T-Mobile, but unfortunately after being the first network to take a chance on Android, they kind of dropped the ball on high-end Android phones. It looks like they’ll be getting the Samsung Galaxy S as the Vibrant, which might solve that problem. (Downside: no camera flash, no physical keyboard, both of which are in the Galaxy S Pro — but I don’t know when or even whether it’ll show up on T-Mobile’s network!)

Also, this doesn’t solve the photo management problem…and if I get a touchscreen-only phone, it’ll really slow down typing until I get used to it.

That and the rumored launch date for the Vibrant is July 21: the day before Comic-Con! That’s not the best time to try to get used to a new device.

2. Get a tablet. As much as I love Apple’s laptops and think that tablet PCs are a great idea, I can’t get behind the iPad. I don’t like the walled-garden approach where Apple gets to choose what you’re allowed to install on your computer. As for other platforms, Windows and Android tablets don’t seem to be comparable just yet.

In short: not gonna happen this year.

3. Get a netbook. I keep coming back to this, don’t I? Last weekend I checked out the selection at Fry’s and Micro Center, and decided on several things:

  • Never, ever buy a netbook without trying out the keyboard first! I found one that was so bad that I’d rather type on my phone for an hour than this netbook.
  • Smaller is better (up to a point). There’s no point in getting a large netbook when I could get a more fully-functional small notebook.
  • A lot of netbooks have truly awful trackpads.
  • While I’d rather get one with Windows 7 than Windows XP, it’s not critical. (Vista, however, is right out. Not that I saw any Vista-based netbooks…)
  • I like the Splashtop instant-on mini-network OS. It’ll be sufficient for 90% of what I’d be doing with a netbook.
  • A big chunk of that other 10% would be photo management! Or at least pulling photos off the camera and uploading them. Managing stuff within Flickr should work.
  • Most netbooks are still above my personal “Oh, just buy it and get it over with” price point, which is $200. MicroCenter had two, one of which was the one with the horrible keyboard, and one of which had Windows XP, didn’t have SplashTop, and had a mediocre trackpad. I really had to think about whether it was worth it or not.

Even so, It’s going to be hard to justify a netbook and a newer phone, and if I have to pick one, it’s going to be the phone. At this rate, by the time I decide to go for it, a tablet may actually be more practical!

An experiment: I’ve modified* Twitter Tools to create digest posts as drafts instead of publishing immediately. That gives me a chance to edit a week’s worth of random thoughts and links down to the interesting stuff, clean things up a bit, expand things that could use more detail, and remind myself of items that I wanted to write more about later.

If it works out, and if the plugin still offers digests after it’s rewritten to use OAuth, I’ll probably use this same setup to make sure I keep on top of linkblogging at Speed Force.

*It was pretty simple. I just looked for the function that creates digests, then changed the post_status from publish to draft.

The Links

  • Why information storage is hard: The Universe Hates Your Data.
  • Interesting analogy: Facebook, Twitter, and the iPhone aren’t quite ecosystems. Maybe it’s better to think of web services as governments. (via ma.tt)
  • WTF of the week: A book I was looking at on Amazon didn’t have any active discussions related to it, so Amazon showed me some random forum threads. They included this question on used textbooks: “Is it Ok if I used it to bludgeon several people to death with it?” Be sure to read the responses. [Edit: Amazon’s forums have been shut down.]
  • I love how Twitter’s status blog describes Wednesday morning’s outage as “high whales.”
  • Dear CNN: A 4.0 earthquake in California, especially one that didn’t cause any damage, is not breaking news. It’s more like business as usual. (It’s worth noting that a full day later, they haven’t updated the story with anything substantive…probably because there isn’t anything to add!)
  • Very cool: the Sci-Fi Airshow is a gallery of photorealistic images of spaceships from various science-fiction TV shows and movies set at, well, an air show. (via Bad Astronomy and SciFi Wire)

Twitter writes that link length shouldn’t matter, but the zillions of URL shortening services out there show that, for now, it does.

But why?

There are two main reasons to shorten* a link:

  • There’s a technical limit, such as SMS message length or email line width.
  • You expect people to manually enter the URL.

Right now, with Twitter messages limited to 140 characters and links forced to share that space with the rest of the post, URL shorteners are critical. But they’re working on a plan to accept longer URLs, and specifically shorten them for SMS messages. The full link will be available on the Twitter website, desktop clients, and other platforms that don’t have that hard and fast limit.

That will cut down on the demand for shorteners, but they’ll still be useful.

For one thing, there are other microblogging platforms out there like StatusNet.

For another, there’s email.

IIRC, the first URL shorteners launched because email programs often break up really long lines, including really long URLs. In plain-text messages, that leaves links not just unclickable, but inconvenient even to copy and paste, because you have to copy each line separately and paste them together. This will continue to be an issue as long as people continue to put visible URLs in email.

And then there’s the human factor. It might not be easy to remember http://is.gd/cGE8V, but it certainly takes a lot less time to write it on a scrap of paper than http://blogs.discovermagazine.com/badastronomy/2010/06/07/hard-to-port-eject-goose-eject/.

Which of those URLs would you rather type on your keyboard? Or worse, on your mobile phone?

*In this case, I mean making it really short and cryptic. There are plenty of reasons to keep links readable and sort of short.

Photo of a door with a sign that says This Is Not a Door.So, remember this photo of a door labeled “This is not a door?” Last year, someone else sent a picture of the same door to FAIL Blog. Then a week ago, someone submitted mine to Friends of Irony, where Katie spotted it a few days later.

Here’s where things get interesting.

On both sites, people were absolutely convinced that it was “obviously” photoshopped.

*headdesk*

No, it’s real. It’s in a small business complex at the corner of Newport Ave. and Irvine Blvd. in Tustin, California. You can go there and look if you want. And of course there are the two photos taken from different angles.

The obvious conclusion is that people don’t really know how to tell whether a photo has been manipulated. At least on FAIL Blog, some of the doubters had reasons, even though they amounted to not understanding perspective.

I was tempted to post a comment linking to this XKCD strip (My hobby: insisting that real-life objects are photoshopped), but settled for requesting a photo credit instead.