I got a Kindle 3! Yay!
All in all, so far, I love this device. I’ve been reading books on my iPhone and iPad so far, but at this point, I’d highly recommend it!
I got the $139 version which has wifi only, but for $189 you can snag a 3G version that will let you download eBooks from anywhere without setting up your own wireless network.
So to start with it, the packaging is very Apple-like. So is the charger. That’s nice. It doesn’t come in a shipping box, the box it comes in IS the shipping box, that’s a damn nice design to avoid wasted packing materials.
Out of the box is a nice experience; the Kindle itself is wrapped in plastic and the screen has instructions on how to get started printed on it. If you want to look like less of a fool than me, you won’t try and pry them off since unlike most devices that have a beautifully printed plastic cover over the screen, the startup instructions are the screen itself! Talk about a great first impression.
Oh, and yes, there is a charger plus a USB cable included in the box. Another nice touch in a day where $300 devices *cough*iPod Touch*cough* don’t include power adapters.
I already have a Kindle account and read eBooks on my iPad and iPhone, when I fired up the Kindle it was pre-configured to my Amazon account and once I got wifi connected, I was immediately able to download books that I’d already purchased.
The screen is absolutely beautiful, the Kindle is so much lighter than I’d expected, and it’s a very comfortable fit in the hand. There are page-turn buttons on the left and right, so it’s great regardless of which hand you’re using at that particular moment.
Unfortunately I did have one fairly major problem with the wifi setup. On the plus side it should work fine for most normal home networks, the problem only occurs when using a configuration that is more common in business networks.
If you really care about the details, read on:
It’s looking like a bug in Kindle’s network stack. Specifically, the device breaks when a DHCP server returns this configuration:
Subnet Mask: 255.255.255.0
Default Gateway: 172.16.0.1
DNS Server: 172.16.0.40
After the Kindle obtains an IP address, it attempts to send a DNS lookups to 172.16.0.40, but routes the packets to the default gateway instead of correctly delivering them to the local network.
Interestingly this works on “normal” home LANs where 172.16.0.1 is both a router and DNS server, but breaks on a more “corporate” style LAN where the router/firewall/default-gateway is not the DNS server.
I’ve reported the problem to Amazon’s support, we’ll see how much hassle it is to get through the first level support droid.