iPhone Tethering, Best Tether Ever

The tethering experience on the iPhone 3G S with iPhone 3.0 OS is slick. Engadget’s how-to can get you up and running. After that, Internet access is attained in 1 step: Plug iPhone in to USB. Nothing more. That’s it. Plug it in and the tether initiates as seamlessly as plugging in a USB ethernet adapter.


Alternatively bluetooth can be used, but incurs the bluetooth bottleneck penalty like other mobile phone tethers. USB allows the full 3G. I’m also partial to leaving bluetooth and wi-fi off to conserve battery life.

So basically you plug in USB and immediately the network connection becomes active. Dead simple. No configuration and no dead phone battery.

Switching from BlackBerry Bold to iPhone 3G S

It’s almost been an annual pilgrimage. Each year since Apple’s release of the original iPhone I’ve jumped in and gotten one, only to get fed up with lousy messaging features and switch back to a BlackBerry.

The phone trail: BlackBerry Pearl 8100 -> iPhone -> BlackBerry 8800 -> iPhone 3G -> BlackBerry Bold 9000 -> iPhone 3G S

I really like the iPhone 3G. I lasted almost a full year, but something was missing. The push, immediate arrival of email, when one can blast messages out and get responses like an instant messaging client, is what I’ve always come back to on a BlackBerry.

This time there’s something different. It wasn’t as impressive with the BlackBerry email. And that must really suck for RIM because I know I’m not the only one who has grown out of their email awesomeness.

Gmail + push based IMAP and Exchange on the iPhone made BlackBerry email much less exciting when I switched back. If RIM can’t own the messaging space, they’re in for some trouble.

The other reason is that my team is doing some great things with the iPhone at Ingram Content. Customers can transfer their downloads through iTunes quickly and seamlessly. I’m using our own product on a daily basis and enjoying it (yes, I’m biased, but it’s still a good sign that a developer wants to eat the comapny’s dog food).

This post was written on the BlackBerry Bold 9000 during my morning train commute. I’ve been listening to Zen and the Art of Motorcycle Maintenance on the iPhone 3G. The upgrade to 3G S is this afternoon. You can download using our Ingram Media Manager for free through your public library.

Flickr + Twitter integration via flic.kr – How to




It was April 6th, 2008 that I posted How to post images to Twitter and Flickr at the same time from an iPhone. It has been one of the more popular posts on this blog.

Flickr now makes it possible to post to Twitter directly via an emailed photo AND via Blog This. Their integration removes the need for TwitPic, and arguably SnapTweet too (though SnapTweet is faster than using Blog This and can be used for multiple images at once).

Images are posted to Twitter with Flickr’s new flic.kr URL shortener.

Here’s how to get set up:

  1. Visit Flickr’s beta testing group’s page (actually, this step isn’t necessary, but if you run in to problems, their page is the best resource).
  2. Associate your Twitter account with your Flickr account here. It leads you through the process and uses OAuth, a safer mechanism than providing your password.
  3. You will be provided with a second special email address to send images to. If your main Flickr image email address is example42test@photos.flickr.com, your Flickr+Twitter email address will be example42test2twitter@photos.flickr.com.
  4. Send away!

Photos sent to your primary Flickr image address will be processed as normal (not submitted to Twitter). Photos sent to your new 2twitter version will be processed and then immediately posted to Twitter. Your tweet will consist of [subject_line] [url], with the [url] being Flickr’s shortened flic.kr url.


After signing up for the Twitter integration you also get a new Blog This addition when viewing a single image. Clicking Blog This brings up the option to post an existing image directly to Twitter. You can post your own, as well as other Flickr users, images via this feature. Very powerful.

Switched from iPhone 3G to Blackberry Bold because of two features

Blackberry Bold 9000

I’ve switched back to a BBerry instead of an iPhone. Again. This is the second time I’ve found I’m working less productively on the iPhone. This isn’t a switch because I enjoy working on a Blackberry. The Blackberry simply handles messaging more quickly and seamlessly, and that’s my impression even after using the iPhone 3.0 OS with copy/paste, etc, for the last couple months.

Don’t get me wrong, the iPhone is the best phone on the market for consuming information. Browsing, the many apps and games, media consumption, appearance, performance, etc, make it the best platform. Ever (imho).

But it still sucks for Gmail and IM and these are the two most important features for a lot of us web jockeys. The native Gmail client on Blackberry enables Gmail searching of multiple accounts instantly. This is a feature worth switching platforms for. The web based Gmail on the iPhone enables such search, but it is web based and takes a lot longer to navigate, even with 3G, and can’t run in the background and perform alerts for new messages.

Background processes enable IM and immediate text communication on Blackberry. I’d gotten by on the iPhone with AIM’s SMS features, which is a nice way to work IM on any phone, but it didn’t cover Jabber and other instant messaging services.

I keep the iPhone in my bag, and continue using it on wi-fi for development and testing. And I can’t wait to get to WWDC and attend the iPhone dev workshops. When the 3.0 OS is out of beta we’ll get to see how these services affect a transition for me, and many others, from Blackberry to the iPhone. Again.

Lunchtime mobile test post, nothing but water to see here…

Twitterlike post…

Grabbing a late lunch and testing a blog post via email. Early this morning I finally set up a cron to check for posts via email.

This post traveled from a Blackberry Bold to Gmail, then the cron ran and the email was pulled by Postie and imported as a post.

Along the way, I ran in to the following problems: – Postie Gmail support – Hosting provider had outgoing ports 993 and 995 blocked – Cronless Postie vs standard (now running cron rev)