My latest trip is coming to a close. Here’s a list of observations on the tools I carried with me on this trip.
The big stuff: Asus Eee PC 1005HA, Droid, iPhone, Kindle.
Only used the Kindle and iPhone a little.
It would be nice to have a bit of web space for me to share data betw the Droid and my desktop. Dropbox isn’t available for Android yet, they just announced its availability for the iPhone.
Surprising that Google is sharing info betw my Droid and my laptop. When I went to movies.google.com on the flight from Atlanta to Boston (it had wifi, not free), it showed me the movies for Atlanta. The only way it could have known I had been in Atlanta was from GPS, I never did anything with either computer to tell it that I had gone through Atlanta. I didn’t mind. But the computer reverted to California for the movies site when I got to Boston.
Droid is a nice but glitchy computer. Hope they smooth it out.
But because of its glitches I tripped over Voice Search which is fantastic. Very accurate, and quite useful. As long as you’re in a quiet place. It freaks out in a cafe or on a noisy street.
I used Google Maps to guide me on a walk from my hotel to Nieman Lab. The GPS is very good and the integration of the GPS with maps is perfect.
The Asus is a much better travel computer than the MacBook Pro — primary reason: battery. There’s a quantitative difference that means you don’t look for power outlets. I’m writing this in the airport lounge at Logan and some people have their computers connected to power outlets. When I got here all the plugs were filled. I’ve been using the computer for about 45 minutes, and only used 5 percent of the power. I’ll make it all the way to Calif on this charge.
I’m using Google’s free wifi in Logan. Thanks!
It’s slow. You have to wonder if they added capacity when they made it free? Or are we all sharing the same pipe they used when it was for-pay?
The biggest bug I found in my new editorial tools is that when the timezone changes the connection to WordPress screws up. I think what’s happening is that it thinks I’m scheduling the post for future publication (because it sees a pubDate is in the future). The problem is cured by hacking the pubdate back a few hours. I’ll have to add the concept of a timezone difference to the tool. I think this will trip up a lot of people.
On the next trip I’ll debug the connection to Tumblr and Posterous.