Skip to main content

Amazon Kindle support oddness

Amazon sent me an odd email regarding the cover for my Kindle.
Dear Kindle User,

We’re sending this note to remind you about proper attachment and use of your Kindle cover and about Amazon’s Kindle warranty. You can view instructions and illustrations here:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200390460

ATTACHING THE COVER
To install the Kindle, open the cover and lay it on a flat surface. Then insert the bottom attachment hook on the cover into the bottom slot on the left edge of the Kindle. Rotate the Kindle to insert the top attachment hook. Then slide the switch down slightly to lock the cover attachment hooks in place.

Be sure to place the Kindle flat on the cover during installation. Do not tip the Kindle at an angle during installation, as that may cause the cover attachment hooks to bend.

USING THE KINDLE COVER
When using your Kindle with the cover, be careful to open the front cover only. If you open the back cover and pull the cover away from the Kindle, that may cause the attachment hooks to bend and could result in cracking or other damage to the Kindle.

THE AMAZON KINDLE WARRANTY
Your Kindle is covered by a One-Year Limited Warranty you can view here: http://www.amazon.com/kindlewarranty

If the attachment hooks on your cover have become bent, or your Kindle has developed cracking or other damage near the location where the hooks connect to the Kindle, please contact Kindle Support by phone or email regarding warranty replacement.

You can reach us via phone or e-mail through our website by clicking the Contact Us button on our help pages at http://www.amazon.com/kindlesupport or directly by calling one of these numbers:
Inside the United States: 1-866-321-8851, Outside the United States: 1-206-266-0927.

For more information, please see the Warranty Service section of the Kindle Return Policies Help page:
http://www.amazon.com/kindlereturnpolicy


Sincerely,
The Kindle Team

Comments

Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.



Advertising!


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

https://api.twitter.com/1/users/profile_image/abraham

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

https://twitter.com/account/redirect_by_id?id=9436992

In_reply_to_status_id mentions:

https://api.twitter.com/1/statuses/update.json?status=reply+to+@abraham&in_reply_to_status_id=12410413197

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

http://a3.twimg.com/profile_images/54160223/chart-black-small.png

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

Assumptions:
LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…