Issues

• Printing the readable content does not currently work on Firefox. This is Firefox's fault, and, unfortuantely, there's no way for me to fix it -- at least no way that is worth the trouble; to both you (the user) and me.
• Readable does not work with NoScript. This is also not Readable's fault. But, unfortunately, I can't really blame NoScript either.

Report an Issue

We're currently using the Issue Tracking on Google Code to manage Readable's issues. (Unfortunately, that means you have to have — or create — a Google acount.)

If you would like to report an issue please go to http://code.google.com/p/readable-app/issues/entry.

Features That Will Not Be Implemented

• I will not turn Readable into an extension, for any browser. I very much like that in it's current form (as a bookmarklet) it works across all browsers and operating systems.
• I will not implement "automatic next page discovery" (example: PageZipper). For long articles (Readable's main use) the error rate would be too high, it would take too much time to perform the operation , and, most of all, the benefit from all of this would be too small.
• I will not add an "Email this page" feature. For one thing, I don't believe it is within my rights to modify someone else's page and encourage people to spread the modified version. For another, I believe that actually mailing the contents of a page is way too mid 90s to still be done today.

Get In Touch

If you would like to get in touch with me regarding Readable, this is the way to do it:

You can also get in touch with me via Twitter. If you'd like, you can even follow Readable App (@readable_app) on Twitter.

Possible reasons to get in touch:

• Report an issue
• Suggest a new font, layout, color, or other CSS setting
• Say 'Hi' — I like saying 'Hi back' to Readable's users