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.
I haven't open sourced the Backend yet, but the reader frontend repo is fully working without the Backend. The Backend is used for emailing yourself and doing file conversion on the Backend instead of the Kindle to save battery.
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.
Why Jailbreak the Kindle when you can just open its browser and visit a website that shows the arrival times?
The Kindle browser is surprisingly decent, I made Claude Code generate an RSS feed reader compatible with the Kindle browser, with the ability to read full articles (for those feeds that require you to visit the website), and download articles. It also supports Reddit and Google News RSS feed. This is my new favorite way of browsing the internet.
Bricked it few times in the process of figuring out more stuff about it, but luckily mine has a UART pads and I was able to restore it every time. A bit more involved as it's 1.8V if I remember right, but if you're careful it should be easy, provided you have the time.
it will be much less power-efficient, when jailbreak you could schedule the kindle to wake up once per 15/30/60 minutes to fetch the new data, set it as screensaver and then go back to sleep.
At no point in human history has C been the best language for beginners. C was, like Javascript, hacked together in a weekend by someone who wished they could be using a better language. It was burdened with flaws from the outset and considered archaic in its design almost immediately. The best thing that can be said about the design of C is that it's at least a structured programming language, which is damning with faint praise.
You’ve just written the exact reason LeeteCode is widely mocked as an interview technique. They are not representative of most real world software, and engineers that train to solve them give a false impression of their ability to solve most other problems.
I’ve interviewed hundreds of engineers for software and hardware roles. A good coding test is based on self-contained problems that the team actually encountered while developing our product. Boil the problem down to its core, create a realistic setup that reflects the information the team had when they encountered the challenge, and then ask the candidate to think it through. It doesn’t matter if they only write notes or pseudo code, and it doesn’t matter if they reach the wrong conclusion. What it’s testing for is the thought process. The fact the candidate has to ask the interviewer questions as though the interviewer is effectively the IDE, is great! The interviewer experiences the engineer’s thought process first-hand. And the interviewer can nudge the candidate in the correct direction by communicating answers that aren’t just typical IDE error messages.
To validate these kinds of questions in advance, I’d often run them on existing team members that hadn’t already been exposed to the real challenge the problem was based on.
Leetcode's utility is not in showing you can solve real-world problems. It's used as a baseline to estimate how smart you are. Every shop prides itself on hiring smart people, and some only want the best of the best—your MIT and Stanford grads, etc. A smarter engineering workforce can not only solve the problems you have, they're better positioned to spot and avoid problems you haven't anticipated yet. Anyways, IQ testing as a condition of employment can open you up to legal liability, as IQ tests are horribly racist. Leetcode is a way around that.
Without commenting on the racial biases of IQ tests (we probably directionally agree), the idea that IQ tests in employment are legally risky is an Internet myth. The companies that offer employment-screening general cognitive tests have logo crawls of giant companies that use them.
They're not unusual because they're legally risky; they're unusual because they don't work well.
It's called Inkfeed
https://inkfeed.xyz
https://github.com/adhamsalama/inkfeed-reader
reply