This setup feels cumbersome, since you also have to manually track which items you have read. Kobo seems to offer better features in this sense (better than a jail broken kindle), however I like the build of my Kindle Oasis 2 too much.
I faced the same issue, but I wanted to use my Kindle to read RSS feeds without relying on my PC, phone or Amazon, so I built a FOSS web-based RSS reader compatible with the Kindle browser. It may make your life a lot simpler.
Hello Adham! Great solution, but I'm having an issue using my Paperwhite 7 Generation in the Kindle web browser. When I try to click on any of the already saved feed, a pop up appears showing the following: loadFeed error: 'undefined' is not an object.
Maybe you have already encountered an issue like this.
Thanks in advance!
It's hard for me to debug this because I don't have a Paperwhite 7. I assume it's a JS compatibility issue but not where the exact root cause.
Since the reader is Open Source, can you run it on your machine and view it on your local network to debug and tell me what's the issue so that I can fix it?
On Kindle 7’s outdated WebKit, both feed loading and article opening failed because the code relied on Set and DOM properties(too modern) that were missing, causing “undefined is not an object/function” errors.
I could fix it by adding defensive null/type checks across DOM and helper functions, and implementing a full Set polyfill (has, add, delete, clear, forEach) to ensure compatibility without changing the existing logic.
Now that I'm checking, the Hacker News articles don't correctly load. Only shows the URL.
It would be great if you opened an issue on GitHub (or a PR) so we can fix this. I definitely want this to work on all Kindles including older models. Thank you.
Nice. I quit my job to build a product[0] to solve this exact problem.
I’m not interested in news but I love reading blog posts, newsletters and interesting technical discussions on HN or reddit.
So I built KTool as a “read it later on Kindle” solution. It supports web links, newsletters (via email forwarding) and RSS. I also added the ability to compile multiple articles into one magazine/ebook and deliver them at a specific time.
I also just did this! My solution was to automate creation of a set of static html pages that I view in the “experimental” kindle browser. It’s set to scrape a paper and build the site at 6am every morning. That was I don’t have to mess with the file transfers, and it’s there waiting for me when I wake up. Also I can mess with the layout a bit easier. Only downside is that I have to have next/back buttons rather than tapping on the screen.
After a couple of attempts I settled on a a different approach for my old Kobo.
It can connect to Dropbox so I deployed a small app in Fly.io which takes a link, bundles it as an epub and uploads to the right folder. Day-to-day all I use is a bookmarklet
Love this approach — using existing hardware creatively instead of buying new gear. The Readeck + Calibre pipeline is clever, especially since Readeck can export directly to ePub.
One thing worth noting: if the "requires a computer" limitation bothers you, KOReader (an open-source reader that runs on Kindle) can fetch RSS feeds and even Wallabag/Readeck content natively over wifi. Might close that last gap without needing a new device.
A while ago I made this to get content from websites for reading in pdf. With what I use (Supernote) you can have an automated script to pull articles in the morning and put them in a dropbox folder that automatically syncs with the device.
Hopefully condoned plug for a service I built, Polyreader (https://polyreader.app), which lets you quickly send articles to your Kindle.
It supports (multiple simultaneous) collections, send via email, saving new articles from links while reading on your Kindle, and little niceties like sending yourself a reminder note at the end of an article ("tell mom this was interesting").
made something with vibe assistance, for generating ebooks from the guardian.com.
the approach here is to self host a web service and download the books from the experimental browser as .mobi for kindle use. These are then fully local and easy to delete after.
https://github.com/tomesparon/guardian-rss-mobi-maker
There's something really satisfying about these kinds of personal pipelines. You stitch together a few tools that weren't designed to work together, automate the glue, and end up with something that fits your workflow better than any single product could. I love it.
I've built a few of these for myself -- a bridge that exposes Apple Notes
over HTTP so I can access them from a Linux VM, a sync tool that pulls Notion
pages down as local markdown. None of them are "products" but they're some of
the most useful things I've built. The common thread is always the same: take
something locked into one device or ecosystem and make it accessible where you
actually want it.
The author's point about not needing a new device is the right instinct. The best version of this stuff is almost always "what can I do with what I already have" before reaching for new hardware.
Btw, I have my own Kindle Oasis, so want to give this a shot!
I did something similar. My computer crawls lite.cnn.com each Saturday. I feed it all into Gemini who composes a "front page" with links in HTML. Then the whole thing is converted to a PDF and uploaded to my Google drive with the day's date as the title. My Boox reader (some Chinese company) is synced to my Google Drive and I just open it from there. I didn't even code any of this, Gemini did.
It's a nice thing to read on Saturday morning with a coffee.
I tried to put together something similar… I guess it is reassuring that others are struggling to find a nice e2e setup as well.
I was intending to vibe code the whole pipeline then stumbled onto Readwise, $10/mo is currently cheap enough to prevent me from building my own.
(I splurged on the Boox so I could easily use/build Android apps on the reader/collection side.)
It does feel like there is a big OSS gap here, and I wish Readwise luck on commercializing too.
From my side the remaining piece is building my own recommendation / crawling pipeline to expand my set of RSS feeds, feels like a good project to add on and Readwise seems quite extensible so it’s a good base to build on.
Any idea why the extension failed? I go to great lengths to make my blog a good web citizen (semantical, working without JS etc.), and that it isn't parseable would be a thing I need to fix.
i created my own rss reader + bookmark list website that i just access through the kindle browser (i dont have it logged into any amazon account though). yours is a cool internet-less idea though!
34 comments
[ 2.2 ms ] story [ 66.4 ms ] threadThis gives you full access to upload whatever ebook you want (SSH, WebDav, Syncthing, ...) and it can fetch RSS feeds (i use it with FreshRSS.)
PS. The (very old) Kindle Oasis is still the best device there is to read on in my opion. Which is crazy, since it was released from 2016-2019...
It has 2 phyisical buttons to turn the page, and an ambient light sensor to auto adjust the brightness, and a 300 PPI display.
I'm still "waiting" for a better / equal device to be released.
[1] https://kindlemodding.org/kindle-models.html
[2] https://github.com/koreader/koreader
Link: https://inkfeed.xyz Repo: https://github.com/adhamsalama/inkfeed-reader
Since the reader is Open Source, can you run it on your machine and view it on your local network to debug and tell me what's the issue so that I can fix it?
I’m not interested in news but I love reading blog posts, newsletters and interesting technical discussions on HN or reddit.
So I built KTool as a “read it later on Kindle” solution. It supports web links, newsletters (via email forwarding) and RSS. I also added the ability to compile multiple articles into one magazine/ebook and deliver them at a specific time.
Give it a try if you’re a Kindle owner.
[0]: https://ktool.io
It could even be paired with an AI summary service that could summarize Reddit/HN activity, like Huxe does in it's generated podcasts.
After a couple of attempts I settled on a a different approach for my old Kobo.
It can connect to Dropbox so I deployed a small app in Fly.io which takes a link, bundles it as an epub and uploads to the right folder. Day-to-day all I use is a bookmarklet
One thing worth noting: if the "requires a computer" limitation bothers you, KOReader (an open-source reader that runs on Kindle) can fetch RSS feeds and even Wallabag/Readeck content natively over wifi. Might close that last gap without needing a new device.
https://github.com/lnenad/newser
It supports (multiple simultaneous) collections, send via email, saving new articles from links while reading on your Kindle, and little niceties like sending yourself a reminder note at the end of an article ("tell mom this was interesting").
It's also cheap (free tier or $1/month).
I keep waiting for Amazon to break mail-to-kindle, but fortunately that hasn't happened yet. Gmail, though... breaks every three months or so.
the approach here is to self host a web service and download the books from the experimental browser as .mobi for kindle use. These are then fully local and easy to delete after. https://github.com/tomesparon/guardian-rss-mobi-maker
I've built a few of these for myself -- a bridge that exposes Apple Notes over HTTP so I can access them from a Linux VM, a sync tool that pulls Notion pages down as local markdown. None of them are "products" but they're some of the most useful things I've built. The common thread is always the same: take something locked into one device or ecosystem and make it accessible where you actually want it.
The author's point about not needing a new device is the right instinct. The best version of this stuff is almost always "what can I do with what I already have" before reaching for new hardware.
Btw, I have my own Kindle Oasis, so want to give this a shot!
[0]: https://github.com/bobek/rannich-5minut-denikn
It's a nice thing to read on Saturday morning with a coffee.
I was intending to vibe code the whole pipeline then stumbled onto Readwise, $10/mo is currently cheap enough to prevent me from building my own.
(I splurged on the Boox so I could easily use/build Android apps on the reader/collection side.)
It does feel like there is a big OSS gap here, and I wish Readwise luck on commercializing too.
From my side the remaining piece is building my own recommendation / crawling pipeline to expand my set of RSS feeds, feels like a good project to add on and Readwise seems quite extensible so it’s a good base to build on.
EDIT: used the firefox extension to save it, pasting the link directly into readeck works :)
But I just tried again and now it saved it correctly.
On my first try it only showed a line of two of the main content, truncated by an ellipsis.