The discussion revolves around displaying approximate reading time in the topic list. meglio suggests that this feature could encourage users to read more topics, citing Medium.com as a positive example. However, codinghorror believes that post count is a reliable indicator of topic length and that users can already estimate reading time.
meglio disagrees, arguing that post count is not an accurate measure of reading time, especially for longer topics. They propose hiding post counts and displaying reading time instead. Mittineague raises concerns about the accuracy of reading time estimates, as they can vary greatly depending on the reader’s intentions (e.g., skimming vs. comprehending).
codinghorror acknowledges that there are exceptions, but believes they are negligible. riking points out that small topics may not have enough data for accurate estimates. meglio suggests displaying “1 min” for topics with estimated reading times of 1 minute or less.
sam notes that it may be possible to create a plugin to inject reading time estimates into the topic list, but expresses concerns about introducing noise.
I’d like to experiment by making it clear to readers that this topic and that topic and that other topic wouldn’t take long to read, so go ahead and read it now!
I know that at medium.com it encouraged me to read more, so I believe it could encourage some else.
In order to do so, I’d like to display the approximate reading time in the topics list.
Is this possible to achieve somehow?
To be fair, I’m the one who hasn’t ever estimated reading time by post count.
So I suppose there are other people like me.
In my mind, there is no big difference between 20 and 30 messages.
But there is some between 7 and 15 minutes.
We can feel time better than the number of messages.
In the first case, I have to calculate / estimate it in my mind.
In the second one, I just get it explicitly.
What is more, it would be interesting to hide the number of posts entirely and show reading time instead, which could make more sense in some cases. I.e. when it comes to 50+ messages, chances are the reader doesn’t care anymore who many more - 60, 70, 120? Does it matter? But when it says 30 minutes or 50 minutes - that could make some sense for the reader.
I caught myself reading more at medium.com just because they inform explicitly that a particular article is only 5 minutes reading or so. So even though the topic may sound not so interesting, why not to give it a try. Then in the middle of the text you find out it was worth starting to read. And you’re more engaged after all. I caught myself doing so, and that’s why proposed this as a feature / plugin for Discourse.
After all, it seems that some topics can have little messages but with really long reflections and write-lover authors engaged, while others can have plenty messages but one paragraph per each.
Conclusion: I’d use it with pleasure if there was such a plugin.
I certainly won’t try to stop you from writing a plugin (or userscript) but such a thing would have problems for me to find it useful.
How would it know if it was something I wanted to simply skim or read and fully comprehend?
i.e. “skim” time would be much different than “comprehend” time.
Going by Title to get an idea of content and post count (though true, post content does vary) works fine for me.