This 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.
I've had my Kobo Clara HD for almost 8 years and I still use it daily with KOReader. It's so easy to install KOReader and it's really repairable. I replaced the SD card at one point, and another time I thought it was broken or needed a new battery but came back to life after reseating cables.
Before that I had a kindle and you had to jump through a lot of hoops to install KOreader, and I remember you had to be careful not to upgrade the firmware so it could be jailbroken.
Like I said I've had the Kobo for 8 years, so I hope this is still the case.
I have been using it like this for a while and it is absolutely bliss to be able to view a catalogue of my inboxed articles on my kindle, with annotation (exports of which are also supported in KOReader).
Koreader is well supported and has all the features you mention.
1. Self host readdeck, add articles to it
2. Have an ebook generated automatically each article saved/day/week/etc
3. Have the ebook be automatically pushed to your jailbroken kindle with KOReader
New side project unlocked, thanks!
That said, I do most of my reading on a Books Palma 2 now. Smaller, so it fits better in a smaller bag or a pocket. And does have physical buttons.
I was a happy Oasis user until last year when I used a new Kindle and saw how much faster they’ve gotten. That started a very frustrating search for a kindle replacement. I ordered and returned many units before settling on the Kobo Libra Color. I didn’t want color, but I don’t notice the lower resolution now unless I’m using it side-by-side with a B&W screen. I do miss whisper sync, which I’d occasionally use to read a few pages on my phone. The Instapaper integration is awesome— I used to pay for KTool to accomplish something similar.
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’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 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).
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.
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 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.
I built readry to solve this issue. It's completely free for forwarding your emails to kindle along with qr codes for images and links so i can open up on my phone if needed
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
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.
It could even be paired with an AI summary service that could summarize Reddit/HN activity, like Huxe does in it's generated podcasts.
It's a nice thing to read on Saturday morning with a coffee.
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?
So without the Backend you're only missing the email feature. All you need is a proxy to bypass CORS.
To be honest I was thinking of keeping the Backend closed source to add subscriptions ($1 per month) to cover the hosting (4$), which means I only need 4 users to break even haha.
Will think about open sourcing the Backend and get back to you.
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.
