MobileRead Forums - View Single Post

awitko · 11-02-2011, 05:18 PM

Read It Later seems to have a lot more features than Instapaper - including searching - and they seem to have a lot more momentum given that they are now venture backed and expanding their team.

The read it now recipe now seems to load 10 articles per page and put it in a separate directory. This arbitrary grouping a separate directory does not make sense. I would think that they should instead be in the same directory. They might optionally be grouped by tags. (If Read It Later eventually imports google reader tags, this would be a nice classification system).

If we run the recipe again, it reloads the previously loaded documents. The instapaper recipe moves the articles to archive after uploading them so that the next upload only takes new articles. Can we do the same on the read it later recipe?

Could we also implement the reverse order option (like we have for instapaper) so that the older article is first in the sequence.

Instapaper (not the recipe) has the option to send to send to kindle on a daily basis if the number of new articles is greater than X (e.g. 10 articles). I think that's a great idea to reduce the volume of uploaded documents to manage on the kindle. It would be great if the recipe counts the number of articles and if its greater than a user specified number it uploads the articles and moves all to archive. If it is less than the minimum article count, it does not upload any articles and does not move any to archive so that these can be uploaded when the minimum quantity of articles is accumulated. It might also have a time feature so that if the oldest unread (non-archived) article is at least Y days old (e.g. 7 days), (Y specified by user in recipe) it uploads the articles even if the minimum number of articles is not met so that articles don't sit there too long before being loaded into the kindle.

I was also thinking that certain read it later articles might be marked as favorites over time after they are read in the read it later service or on the kindle or other reader. It might be nice to have a second recipe that uploads only the favorites into an e-book, optionally in directories by tags. This might include archived and "unread" documents so that this is an all time favorites e-book on your kindle. It would not update the unread/archive status. The previous recipe would be a periodical of recently saved documents for deletion after reading and this recipe would create an updated e-book of all time favorites so that they are always handy on the e-reader.

Alex

11-02-2011, 05:18 PM	#1
awitko Member Posts: 23 Karma: 10 Join Date: Oct 2011 Device: Kindle	Read It Later Recipe Read It Later seems to have a lot more features than Instapaper - including searching - and they seem to have a lot more momentum given that they are now venture backed and expanding their team. The read it now recipe now seems to load 10 articles per page and put it in a separate directory. This arbitrary grouping a separate directory does not make sense. I would think that they should instead be in the same directory. They might optionally be grouped by tags. (If Read It Later eventually imports google reader tags, this would be a nice classification system). If we run the recipe again, it reloads the previously loaded documents. The instapaper recipe moves the articles to archive after uploading them so that the next upload only takes new articles. Can we do the same on the read it later recipe? Could we also implement the reverse order option (like we have for instapaper) so that the older article is first in the sequence. Instapaper (not the recipe) has the option to send to send to kindle on a daily basis if the number of new articles is greater than X (e.g. 10 articles). I think that's a great idea to reduce the volume of uploaded documents to manage on the kindle. It would be great if the recipe counts the number of articles and if its greater than a user specified number it uploads the articles and moves all to archive. If it is less than the minimum article count, it does not upload any articles and does not move any to archive so that these can be uploaded when the minimum quantity of articles is accumulated. It might also have a time feature so that if the oldest unread (non-archived) article is at least Y days old (e.g. 7 days), (Y specified by user in recipe) it uploads the articles even if the minimum number of articles is not met so that articles don't sit there too long before being loaded into the kindle. I was also thinking that certain read it later articles might be marked as favorites over time after they are read in the read it later service or on the kindle or other reader. It might be nice to have a second recipe that uploads only the favorites into an e-book, optionally in directories by tags. This might include archived and "unread" documents so that this is an all time favorites e-book on your kindle. It would not update the unread/archive status. The previous recipe would be a periodical of recently saved documents for deletion after reading and this recipe would create an updated e-book of all time favorites so that they are always handy on the e-reader. Alex Last edited by awitko; 11-02-2011 at 06:31 PM.