Is it just me, or was that article more fluff than anything else?
I have a Kobo ereader and so use Pocket for saving articles that I want to read later, away from the computer. Have found it works very well for this. (That said, if my ereader integrated Instapaper or Readability I’d probably be just as happy.)
My one complaint is that every now and again it finds an article it cannot extract the main content from. In that case it never ends up on my ereader, and there’s no obvious indication that there is a problem.
To track my readying habits, I wrote a little PHP browser based application that interfaces with the Pocket API (and the hn.algolia.com API). Once I’ve read an article I archive it. Then when I’m back at my computer I run my app, which lists the archived articles, any related Hacker News pages, and lets me manage the articles (delete, save locally, etc.). It makes it easy for me to follow up and read the HN discussions after I’ve found the time to read the article.
I have a Kobo ereader and so use Pocket for saving articles that I want to read later, away from the computer. Have found it works very well for this. (That said, if my ereader integrated Instapaper or Readability I’d probably be just as happy.)
My one complaint is that every now and again it finds an article it cannot extract the main content from. In that case it never ends up on my ereader, and there’s no obvious indication that there is a problem.
To track my readying habits, I wrote a little PHP browser based application that interfaces with the Pocket API (and the hn.algolia.com API). Once I’ve read an article I archive it. Then when I’m back at my computer I run my app, which lists the archived articles, any related Hacker News pages, and lets me manage the articles (delete, save locally, etc.). It makes it easy for me to follow up and read the HN discussions after I’ve found the time to read the article.
Naturally I called it Pocket Lint.