Show HN: I built a tool to help you read Hacker News on Kindle
393 points| longnguyen | 3 years ago |ktool.io | reply
The idea of KTool first came to my mind when I was reading "Ask HN: I'm a software engineer going blind, how should I prepare?"[0]
I've been wearing glasses since I was 5. My right eye is basically blind. Doctors said there is no chance to cure it.
I was genuinely scared. Like holy shit, if my left eye stops working, my life is done. Since then I've been very conscious about time spent on computer screens.
That's when I started using Kindle-related products: to offload as many reading materials as possible to the Kindle. I was a happy customer of Push to Kindle. Great product!
Then I ran into multiple limitations which led me to build KTool: a tool to send anything online to Kindle. Blog posts, Twitter threads, Hacker News discussions, RSS, newsletters... you name it.
But I'm not here to pitch my vision for KTool.
I built a specific tool to help you send HN discussions to your Kindle. And in the spirit of Show HN, it doesn't require an account. If you don't own a Kindle, there is the option to download the EPUB.
Let me know what you think. Any feedback will be much appreciated.
If you're a Kindle owner and you read a lot of online content, give KTool a try.
[+] [-] Abishek_Muthian|3 years ago|reply
Congratulations on the launch!
I received an email from HN user telling me about this post because a while back I was running 'HN to Kindle' service[0] and since Amazon enabled 2FA for bulk emails even for approved email ids I lost motivation to run it further and instead made the core application open-source[1].
Since you're sending HN item individually, I'm not sure whether you'll face the 2FA block but do monitor whether your users are getting your emails delivered by connecting with them.
Your website's presentation is way better than mine, Perhaps because you've put JS to good use. Feel free to use my code to implement other features like classification according to chosen topics if you'd like it.
[0] https://web.archive.org/web/20220216140431/https://hntokindl...
[1] https://github.com/abishekmuthian/hntoebook
[+] [-] longnguyen|3 years ago|reply
Yeah I haven't run into the 2FA issue yet, but probably will. Is there any docs about this 2FA issue I can read (other than the short doc on amazon.com)?
Thanks,
[+] [-] mft_|3 years ago|reply
First, I love what you've done here, and why - congratulations on making it this far!
A few suggestions:
1) An independent web route is important, but you could lower the friction even further with browser plugins. Like you, for general articles I use push-to-kindle[0] which only needs two clicks - no copy/paste, etc.
2) Have you also thought about including a copy of the original article - so that in a single download, there's the article followed by the HN discussion, all accessible from the document's index?
3) I could see this developing further as a productivity tool via subscription - maybe I set up an account with you and then receive a digest of the day's top-10 (or 20, whatever) articles and discussions. Or a weekly digest? Might be a powerful way to divert people away from the regular distraction of HN, but still allow consumption.
Good luck :)
[0] https://www.fivefilters.org/push-to-kindle/
[+] [-] longnguyen|3 years ago|reply
1. I've actually developed that[0]. Using the browser extension is even more powerful as it could send content behind paywalls to Kindle — something not possible for the web UI.
The reason I didn't mention it is it requires an account, probably not a good thing for a Show HN.
2. Yes. I'm not sure if that's a useful feature, but personally, I don't like it. I want the original article to be a separate ebook so highlights & notes go into the correct entry. But that's an interesting feature for sure. Probably will make it a user preference.
3. Yes! That's 100% on my road map. And not just for HN. I got beta support for newsletters now but it doesn't work with a digest-type newsletter.
Thank you again!
[0]: https://ktool.io/install
[+] [-] Bluecobra|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply
I find computer screens cause more eye strain than Kindle.
Yeah, I don't think we can avoid screens completely. I just wanted to offload some of the reading to the Kindle. So I could read outside more.
[+] [-] colincooke|3 years ago|reply
[+] [-] tcmart14|3 years ago|reply
[+] [-] Bakary|3 years ago|reply
I also suggest trying Android e-ink readers from companies such as Hisense or Onyx Boox as they've come a long way in the last few years. (Not affiliated with them, just a bit obsessive on the topic)
With the upcoming generation of color e-ink and large companies starting to notice (Apple, Huawei) it's only going to get better and better moving forward.
[+] [-] wiseowise|3 years ago|reply
No way I’m going to support company like that.
https://www.reddit.com/r/Onyx_Boox/comments/hsn7kx/onyx_usin...
[+] [-] criddell|3 years ago|reply
[+] [-] password4321|3 years ago|reply
I see what you did there.
Didn't Amazon tighten up how custom content is delivered to Kindles fairly recently, requiring 2FA? So you need to connect the Kindle to load the content?
[+] [-] longnguyen|3 years ago|reply
So far I haven't run into the 2FA issue yet. I made sure the email configuration was correct (all those SPF, DKIM, DMARC kinds of stuff) and the KTool email was added to their Approved email address list.
[+] [-] lolinder|3 years ago|reply
Here's the help article describing that process: https://www.amazon.com/gp/help/customer/display.html/?nodeId...
[+] [-] oidar|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply
1) You are right. I build KTool with privacy in mind and I've thought about this. There is always the option to set it up manually[0][1] but probably it wasn't obvious. I'm open to any UX suggestion here.
I should mention that the KTool extension doesn't require any special permission, unlike Instapaper which asking to access your webpages _all the time_[2]. KTool cannot access the web pages you visit until you click on the extension icon and perform an action.
2) Yeah and the instructions for the iOS extension is not even clear. I developed it for some of my paying customers and haven't paid much attention yet. Thanks for the feedback.
PS: don't listen to the Internet. The new Web Extension is not better than building a Share Extension.
3) Great idea. Will implement that next.
4) There is always the monthly subscription option[2] and this UI/UX is pretty common among SaaS. I'm not sure how can I make it more obvious. Again, any UX suggestion is welcome.
[0]: https://share.cleanshot.com/AOk1Ii
[1]: https://share.cleanshot.com/wLrjRh
[2]: https://twitter.com/daniel_nguyenx/status/155730594021050368...
[3]: https://share.cleanshot.com/sqrUzZ
[+] [-] nabaraz|3 years ago|reply
My feedback: I can't justify paying $4/month to be able to send few packaged webpages to my kindle, If this was a one time payment of ~$20, I'd be interested.
[1]. https://chrome.google.com/webstore/detail/send-to-kindle-for...
[+] [-] longnguyen|3 years ago|reply
Most of the time, the official extension doesn't work for me. And I'm not alone. You can check their recent reviews[0]. A lot of 1 star.
I'm aware that there are other alternatives such as Push to Kindle, P2K, Instapaper, newslettertokindle etc. They provide much better conversion quality than the official extension, and better deliverability. I'm confident that KTool is on par with them, maybe better in some use cases (such as Twitter threads, HN, sending pdfs...). And their paid plans range from $2.99/mo to $10/mo.
What I'm doing at KTool is to support all those content in a single subscription.
I hate subscriptions, but until we found a better model, I can't sell it as one time payment. My expense is recurring (CPU for parsing & image processing, email + bandwidth to send articles to Kindle, Apple developer program, core parser maintenance as sites structure changes...)
But I will definitely do more experiment with pricing though.
Again, thanks for your valuable feedback. Much appreciated
https://chrome.google.com/webstore/detail/send-to-kindle-for...
[+] [-] dchuk|3 years ago|reply
[+] [-] jeffbee|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply
[+] [-] xena|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply
[+] [-] nik5|3 years ago|reply
[0] https://github.com/nikhil1raghav/kindle-send
[+] [-] cgb223|3 years ago|reply
Kindles can only (easily) do what Amazon wants it to do —full stop.
It’s like the iPhone before the App Store.
I bet Amazon would make a massive amount of money if they opened up their ecosystem to let others develop on top of it
[+] [-] criddell|3 years ago|reply
If I were head of that division at Amazon, I'd remove bluetooth, APIify the bookstore (so you can buy books from other retailers), remove GoodReads integration, and direct the hardware people to focus on battery life and the software people to focus on layout and typography. I'd also add a physical switch to enable/disable the touchscreen. All Kindles would have physical page turn buttons like the Oasis does.
[+] [-] donio|3 years ago|reply
I use my regular e-ink kindle 100% offline, I never turn off airplane mode. I only load content via USB using the Calibre CLI. I don't want my Kindle to do cool stuff. I used to think I did, I rooted my early Kindles and tried to do as much on them as possible. But then I realized that it's only a distraction from the one thing the Kindle is actually good at: reading long static text documents.
[+] [-] protonbob|3 years ago|reply
[+] [-] azinman2|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply
Meanwhile, you can sign up for an account and send articles using the main product (the browser extension).
[+] [-] SnooSux|3 years ago|reply
What has that been like?
[+] [-] longnguyen|3 years ago|reply
[+] [-] catchmeifyoucan|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply
[+] [-] johnthescott|3 years ago|reply
combining HN and kindle is intriguing. my most serious work occurs laying in bed reading, before falling asleep. i will surely follow your work.
[+] [-] testmasterflex|3 years ago|reply
[+] [-] jhoelzel|3 years ago|reply
[+] [-] novantadue|3 years ago|reply
[+] [-] futhey|3 years ago|reply
[+] [-] longnguyen|3 years ago|reply