Next

View counters in feeds are inconsistent because they are displaying the number of views in the specific feed, and not the total number of views.

Steps to reproduce

Go to top 12 hour video feed and observe the view count on a post. Next go to the channel page of that content creator and notice that the view counts on the original post are not synched with the top feed.

Platform information

win10 chrome

What is the current bug behavior?

inconsistent view counters on content

view counters should synch real time or near real time

counters should be consistent from feed to feed

Relevant logs and/or screenshots

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

added 0 - Urgent P - Messenger T - Bug labels

changed the description

(edit): Sorry, wrong issue, re-opening

closed

mentioned in issue minds#376 (closed)

reopened

I believe that this is related to caching issues, that are known about and high priority. @markeharding can you confirm?

added 1 - High label and removed 0 - Urgent label

added Bug Hunter label

No, they are totally separate entities so thats why the views are showing as different.

The fact they are different entities is the problem! There should be just one!

Regards,

John Ottman Chairman and Co-founder Minds, Inc. (203) 856-6081

@Johnthetester firstly, take your phone number off of here probably? secondly, let's keep the architectural suggestions to the developers! you aren't considering the context of why different feeds require different entities :)

The counters as separate objects should should synch.... otherwise there is data consistency issue that is quite confusing to a user experience.

Regards,

John Ottman Chairman and Co-founder Minds, Inc. (203) 856-6081

I do not see any phone number where is that displayed? Screen shot?

Regards,

John Ottman Chairman and Co-founder Minds, Inc. (203) 856-6081

So this isn't a technically a bug, because its intended functionality. That isn't to say you don't still have a valid point; it is still confusing to users - I agree... Perhaps this should be converted into a feature request?