Hello!
I’m not exactly sure how to word my title. But I think the DevForum could improve all post/topic read time and detection. By “detection” I mean detecting if the user is actually reading the post, and not just scrolling by.
-
Once I clicked on a topic, and went to grab something, and when I came back the topic was marked as read, even though I hadn’t read a single word yet. The topic was also added to my stats “Topics Viewed”
-
This could also make user stats more accurate, and the number of posts read by a user would be more accurate and actually read by the user. I’m sure there are people out there that will cheat/abuse the read detection system. (I am not pointing anyone out, just saying that this is happening.) They cheat so that posts and topics are marked as read, even though they didn’t read a single word from it.
DISCLAIMER: I will not mention particular strategies they use to cheat/abuse the system. I feel like that may give users ideas and motivations to further cheat. (They are cheating, not exploiting)
-
Some users have mentioned this, but make sure not only does a post mark as read after literally reading it, but make it actually work. Sometimes I will read a post, and it will still be marked as unread, even if I stay on it for like 5 minutes.
-
Once I created a topic asking for a solution to a problem I had. Then there were people who mentioned one particular solution to my problem. What they didn’t realize was that I had clearly mentioned that solution in my topic beforehand and said that it didn’t work. So clearly they just ignored it, didn’t have other answers, or just didn’t read that section. So I clarified that as a reply, and then? The next day there were more people who brought up the same solution, and I had now mentioned twice that the particular solution they brought up didn’t work. I mean, generally the longer your topic is the less time and effort people will spend reading your entire topic. And the topic I wrote was decently lengthened. (But that doesn’t act as an excuse.)
I am not trying to aim this at anyone, just saying that the above happens (pretty commonly) and should be fixed.
I know this can be bypassed, but maybe create a system where instead of just marking a topic as read after a few seconds, mark it as read if after the user reads the entire topic from top to end, meaning they will have to scroll down.
Don’t know if this is already in place, but make it so that the user can only reply after reading the entire topic.
Also maybe create certain buttons a user must periodically click that is randomly generated on the screen, and the user will be kicked out if he/she doesn’t respond after a certain time. This may be pretty annoying, but I can’t really think of any other solutions. (That’s why you guys should share yours!)
Anyway, sorry for the long post; I wanted to be as specific as I could to address this issue.
Anyway, have a nice and fantastic day!