The new WordPress iPhone app is quite nice. Very clean integration. Seamless, but support for post plugins like Flickr images seem to be a problem.
It’s a great new world when we can blog and participate, without limitation, from a pocketable handset.
The pic is a snap of my N82 here at a diner over lunch.
… 
I picked up the Nokia N82 yesterday from Import GSM, a great hybrid brick-and-mortage / online store. Think Dynamism for phones. It was my first visit, right at closing, and despite trying to get stuff out the door for the evening shipment the guys helped out with descriptions and subtle nuances between the N95 and N82 (special thanks to Eric – good guy).
Anyway, so why the heck would someone get a Nokia N82 when the iPhone 3G is getting released tomorrow? There are five reasons, one for each megapixel, and a lot of backup arguments. The iPhone 3G doesn’t hold a candle to the image sensor quality, flash, or lens quality.
This wasn’t meant to be an N82 vs. iPhone 3G post. They’re both the best mobile equipment one can get (imo).
The N82 is going to be my net enabled camera and broadcast machine. No more notebook + Canon SD-1000 combo!
The iPhone 3G is for everything else. I had the iPhone (1.0 / original / whatever). iPhones are the best for usability and communication. I gave it to my wife and she’s gone from check-email-and-browse-at-home to check-email-send-texts-and-monitor-weather-while-away. The wife-o-meter was pegged.
The Nokia’s OS, after 30 hours of tweaking, is finally usable for me. Very steep appreciation curve. I would only recommend such a phone to a power user needing the best tool for quality images… I can’t wait to start posting and qik’ing them.
Watch this walking tour of the Washington DC Newseum. My new favorite museum!
This video was a fun experiment in video blogging.
Tools used:
Canon SD-1000, 640×480 @ 30fps
iMovie
Viddler for commenting (uploading to other services for comparison)
Chris Bilson (@cbilson) had a good description regarding my post about Twitter’s scaling/architecture challenge.
“Kevin Rose and Leo Laporte tweet at the same time = crossing the streams”
I dunno if Proton Packs have exponential load challenges, but the end result for a server can feel similar. Is my post I pointed out that Twitter has to determine delivery options and potentially deliver between 100 million and 1 billion updates per day.
But that’s in a day. 1 billion messages in a day are a piece of cake when spread over 24 hours. What if 1 billion messages have to be delivered in an hour? Or all at once?
Take my list of the top-10 Twitter accounts and imagine them all at TED, WWDC, Google I/O, or your local unconference. These ten users, if each sends an update around the same time create 321,928 messages that need delivery (total number of followers for top-10 accounts). This is an awesome amount of message delivery. If those ten users live-blog or get conversational and send ten updates in an hour… 3,219,280 (again, that’s from only 10 users).
I don’t illustrate this to state it’s these power user’s fault. Absolutely the opposite. They’re generating amazing amounts of traffic, which is a wonderful thing, and the algorithms are the problem.
It’s possible to optimize algorithms and modify systems for maximum performance. I bring up Twitter’s challenges because I’m wondering if this is a challenge beyond present day computing.
To open some minds, here’s an impossibility often overlooked: Huge numbers in a deck of cards (just to show impossibilities can stem from small initial numbers).
Thanks to new Twitter user @waileacapital for posting about a British woman, Roz Savage attempting to row across the Pacific (she rowed across the Atlantic already). If she succeeds she will be the first woman to complete the journey.
Roz blogs on a daily basis during a trip at http://rozsavage.com/blog. Her main site is at http://rozsavage.com. The video above is of her Atlantic trip.
The latest is that she is having trouble with her desalinization system and having trouble getting fresh water.