4 ms·

Readability is amazing. I find it works most of the time. Currently I'm using it to parse a web article, package into a .mobi file and send it directly to my K

Readability is amazing. I find it works most of the time. Currently I'm using it to parse a web article, package into a .mobi file and send it directly to my Kindle Paperwhite. If you want to read your favorite content on Kindle, give it a try[0] [0]: https://ktool.io https://ktool.io

zulln 5y ago
For websites, do you have examples where it outperform Amazon's own solution? https://www.amazon.com/sendtokindle/ https://www.amazon.com/sendtokindle/
- longnguyen 5y ago
  KTool[0] is fairly new so I can't claim it "outperform" Amazon's solution. However if you read the recent reviews from their Chrome Extension page[1], the majority of complaints was that the article never arrived. I just tried sending this article[2] and 10 minutes later it still hasn't delivered yet. This article contains a lot of images, so I understand it's not going to be quick, but with KTool, it does deliver within 2 minutes. But that is not the only reason why I build KTool. I don't want the articles to include links when reading on my Kindle because it's bad UX (easy to mis-tap), distracting and reduce comprehension (see here[3] and here[4]). Instead, I push all these links to the bottom of the article, which make it still accessible yet improve the reading experience. [0]: https://ktool.io https://ktool.io [1]: https://chrome.google.com/webstore/detail/send-to-kindle-for-google/cgdjpilhipecahhcilnafpblkieebhea https://chrome.google.com/webstore/detail/send-to-kindle-for... [2]: https://waitbutwhy.com/2017/04/neuralink.html https://waitbutwhy.com/2017/04/neuralink.html [3]: https://www.wired.com/2010/05/ff-nicholas-carr/ https://www.wired.com/2010/05/ff-nicholas-carr/ [4]: https://www.roughtype.com/?p=1378 https://www.roughtype.com/?p=1378
  - longnguyen 5y ago
    Update: 5 hours later, no sign of the article being delivered. It think it's safe to assume the Amazon solution doesn't work ¯\_(ツ)_/¯
alexdoesstuff 5y ago
This is amazing! Do you have any ideas on how to use it to send content behind paywalls to the Kindle?
- longnguyen 5y ago
  Well, I won't implement such feature since I don't want to be part of a legal dispute. But I'm working on a feature where you can send content from client side. Meaning you can use any other extensions to modify that page's content[0]. KTool Extension will take that content as input, parse and then send to your Kindle. [0]: https://chrome.google.com/webstore/detail/bypass-paywall/kkofljmpfaanangehehmbkkmbgjjlgja https://chrome.google.com/webstore/detail/bypass-paywall/kko...
  - alexdoesstuff 5y ago
    I wasn't actually suggesting bypassing paywalls (in case it came across like that) but rather taking content that a user has access to but that is not accessible by a third party - such as paywalled content, content behind login screens, etc. An extension seems like a natural way to accomplish that.
    - longnguyen 5y ago
      Ah gotcha. Yes, I'm already working on a browser extension for that. That's also the main differentiator to my competitors. Hey you can sign up for an account to receive updates, or just reach me directly via email. My email is on my profile. Thx

zulln 5y ago

For websites, do you have examples where it outperform Amazon's own solution? https://www.amazon.com/sendtokindle/ https://www.amazon.com/sendtokindle/

longnguyen 5y ago
KTool[0] is fairly new so I can't claim it "outperform" Amazon's solution. However if you read the recent reviews from their Chrome Extension page[1], the majority of complaints was that the article never arrived. I just tried sending this article[2] and 10 minutes later it still hasn't delivered yet. This article contains a lot of images, so I understand it's not going to be quick, but with KTool, it does deliver within 2 minutes. But that is not the only reason why I build KTool. I don't want the articles to include links when reading on my Kindle because it's bad UX (easy to mis-tap), distracting and reduce comprehension (see here[3] and here[4]). Instead, I push all these links to the bottom of the article, which make it still accessible yet improve the reading experience. [0]: https://ktool.io https://ktool.io [1]: https://chrome.google.com/webstore/detail/send-to-kindle-for-google/cgdjpilhipecahhcilnafpblkieebhea https://chrome.google.com/webstore/detail/send-to-kindle-for... [2]: https://waitbutwhy.com/2017/04/neuralink.html https://waitbutwhy.com/2017/04/neuralink.html [3]: https://www.wired.com/2010/05/ff-nicholas-carr/ https://www.wired.com/2010/05/ff-nicholas-carr/ [4]: https://www.roughtype.com/?p=1378 https://www.roughtype.com/?p=1378
- longnguyen 5y ago
  Update: 5 hours later, no sign of the article being delivered. It think it's safe to assume the Amazon solution doesn't work ¯\_(ツ)_/¯

alexdoesstuff 5y ago

This is amazing! Do you have any ideas on how to use it to send content behind paywalls to the Kindle?

longnguyen 5y ago
Well, I won't implement such feature since I don't want to be part of a legal dispute. But I'm working on a feature where you can send content from client side. Meaning you can use any other extensions to modify that page's content[0]. KTool Extension will take that content as input, parse and then send to your Kindle. [0]: https://chrome.google.com/webstore/detail/bypass-paywall/kkofljmpfaanangehehmbkkmbgjjlgja https://chrome.google.com/webstore/detail/bypass-paywall/kko...
- alexdoesstuff 5y ago
  I wasn't actually suggesting bypassing paywalls (in case it came across like that) but rather taking content that a user has access to but that is not accessible by a third party - such as paywalled content, content behind login screens, etc. An extension seems like a natural way to accomplish that.
  - longnguyen 5y ago
    Ah gotcha. Yes, I'm already working on a browser extension for that. That's also the main differentiator to my competitors. Hey you can sign up for an account to receive updates, or just reach me directly via email. My email is on my profile. Thx