As long as the Kindle includes a browser which can access the web, we have access to these items.

The clause states “personal, non-commercial documents” which kindlefeeds are.

It goes on to forbid “the sending of documents from automated distribution services” which could be taken to apply to kindlefeeder if you use the scheduled push option.

My personal feeling is that Amazon would do best to embrace the additional value that folks like Dan are creating for the Kindle. This user community is free and tireless (as a whole!).

If there is cost associated with this, Amazon has a right to recover those costs, but since Amazon hasn’t even turned on the $.10 charge yet, it’s hard to believe they are feeling a ton of angst over this.

The result would be the same in every way, except the users would be sending the content (prepared by kindlefeeder) to Amazon for conversion and delivery. Would this be in violation of the clause?

Also, the clause seems to forbid all non-personal, non-commercial documents. Is RSS content non-personal? Is personalized RSS content personal enough? Like Kenneth, I’m confused by the meaning of these terms.

That’s why I created the Kindle guide first (http://www.feedbooks.com/help/kindle#guide) and decided to use a similar system for the RSS feeds.
To auto-sync the content, I use our API and a companion software: NewsStand (http://www.feedbooks.com/help/newsstand) which automatically update your content as soon as you plug-in our device.

You’re right Kenneth though, that while Amazon would probably ban such a service, it’s unlikely that they would limit the same software if you’re the one who automatically send the feeds to your Kindle. You can do this using Daniel Choi’s tool, or with a simple wget on the files generated by Feedbooks (anyone could build a tool that e-mail themselves files from Feedbooks).

I think that most people are wrong when they believe that they really pay for blogs (the content) on the Kindle. What they pay for, is the service: automatic & wireless delivery. They know that the only way for a generic service to compete with their blog delivery, is to offer automatic e-mail delivery.

On the other hand, I think Amazon should strongly reconsider restricting the Kindle this way and perhaps after people try using kindlefeeder.com they’ll start agreeing with me.

As a programmer, I wanted to make software tools to extend the Kindle’s capabilities and make it work in more convenient ways. And so I created two tools in the last month: an open-source command-line tool called kindle-feeds (covered before by teleread.org) and now the automated feed delivery service, kindlefeeder.com.

If this is something Amazon wants to prohibit, I suppose Amazon is fully within its rights to do so.
Amazon can shut kindlefeeder.com down at any point simply by rejecting the emails sent from kindlefeeder.com to its conversion service. This may happen soon, now that teleread has posted this post.

But until then, I will leave kindlefeeder.com up in the hope that the site can at least stimulate a discussion about this restriction by Amazon on Kindle users’ freedom to use their Kindles as they see fit.

If the issue is that allowing independent automated distribution services to delivery content to Kindles would increase the processing burden on Amazon’s document conversion and delivery service, it would be healthy to have a discussion about how Amazon might accommodate user demand for such services without losing money AND without overly restricting the freedom of their users and software programmers who are interested in making tools for them.

This is a discussion Feedbooks would benefit from too! I think Feedbooks’ RSS service for Kindle users is excellent, but the fact remains that the lack of automation and scheduling IS an inconvenience for users. It’s a shame that Amazon (apparently) wants to keep the power of automating the delivery of content all to itself. I’m hoping Amazon changes it mind, and takes a step toward making the Kindle a slightly more open platform.

That’s part of the reason (aside from the 10 cents) why I’m not interested in implementing such a thing on Feedbooks: I’d rather avoid doing exactly the opposite of what Amazon authorize.

In the user guide: “The conversion service on Your Kindle is meant for the receipt of personal, non-commercial documents only. You may not authorize the sending of documents from automated distribution services.”.