Show HN: Estimated Reading Time API
klopets.com
Show HN: Estimated Reading Time API
1–10 of 30 posts
Re: Show HN: Estimated Reading Time API
#2Nice demo! Is this code for this available online? I'd love to see how this works.
Re: Show HN: Estimated Reading Time API
#3Why do we need an API for this? A library seems easier, and even that is a stretch for doing `$wordcount / 200 = minutes required to read`. Does this make an estimate of the article's complexity and adjust how many words a person reads per minute?
(Source for 200 words per minute: https://en.wikipedia.org/wiki/Words_per_minute#Reading_and_c... )
Re: Show HN: Estimated Reading Time API
#4Why do we need an API for this? A library seems easier, and even that is a stretch for doing `$wordcount / 200 = minutes required to read`. Does this make an estimate of the article's complexity and adjust how many words a person reads per minute? (Source for 200 words per minute: https://en.wikipedia.org/wiki/Words_per_minute#Reading_and_c... )
We definitely don't need an API. Then again, we basically don't need most APIs. This doesn't estimate the article's complexity as of now, but its main point is not just getting the length of the entire site, but locating the most likely main content area and THEN doing the /250.
Re: Show HN: Estimated Reading Time API
#5Is this specially good? Does it use a better algorithm or something?
Just asking because there's no explanation, and it would be probably better to hack something in JS than to depend on this probably-soon-to-vanish-api. There's already https://eager.io/app/reading-time, for example, which anyone can install in 2 minutes, and is based on a simple algorithm[1], it seems.
[1]: https://github.com/TeffenEllis/reading-time/blob/master/app....
Re: Show HN: Estimated Reading Time API
#6There is a plugin[1] for people that blog with Pelican for this. It also will score your Flesch-kincaid[2] values. You can see it in action on my blog: http://caffeineindustries.com/
I do think I should adjust the words per minute values...
[1] https://github.com/getpelican/pelican-plugins/tree/master/po... [2] http://en.wikipedia.org/wiki/Flesch%E2%80%93Kincaid_readabil...
Re: Show HN: Estimated Reading Time API
#7Nice demo! Is this code for this available online? I'd love to see how this works.
This is just that - a demo right now. I'll most likely keep this as a pet project of mine, trying to make the underlying algorithm a bit more intelligent. I'll then probably release it on GitHub (https://github.com/mklopets).
Re: Show HN: Estimated Reading Time API
#8A bit too simple for an API, reminds me of Fuck Off As A Service. http://www.foaas.com/
Re: Show HN: Estimated Reading Time API
#9We've officially reached Peak API. What's the algo?
Re: Show HN: Estimated Reading Time API
#10Why do we need an API for this? A library seems easier, and even that is a stretch for doing `$wordcount / 200 = minutes required to read`. Does this make an estimate of the article's complexity and adjust how many words a person reads per minute? (Source for 200 words per minute: https://en.wikipedia.org/wiki/Words_per_minute#Reading_and_c... )
We definitely don't need an API. Then again, we basically don't need most APIs. This doesn't estimate the article's complexity as of now, but its main point is not just getting the length of the entire site, but locating the most likely main content area and THEN doing the /250.
You can use something like:
https://github.com/grangier/python-goose
https://pypi.python.org/pypi/textstat/
+ using word counts that adjust for reading ease