Are known bots (google, etc) handled specially, or are they just normal anonymous views?
Also, given this explanation, the column should really be named âViewersâ (or maybe âReadersâ) since thatâs what itâs really trying to show. Saying âViewsâ and only counting viewers as is being done is very confusing.
Not yet, I do want to improve this just donât even know what a âgoodâ views algorithm is. Is trivial considered âgoodâ.
I think we need to take this discussion a bit full circle, how would your idea views thing work?
The advantage of âtrivialâ is that it is probably really transparent and obvious. Now that I understand what the current view number means, it makes sense. But it still seems weird to see many topics with more posts than views. Maybe certain types of forums are more susceptible to this than others.
I think the concept of allowing the view counter to increment for a user after 8 hours makes sense. As mentioned, the current method seems to under value logged in views. If I go to a particular conversation every day, Iâm showing a fair amount of interest in it compared to going once and then ignoring it. Even if Iâm not saying anything, Iâm reading and paying attention to it (maybe posting Likes, too).
The trivial method would seem to be open to abuse, probably including DDoS.
8 hour method has a big advantage as well, you cut down on storage drastically, cause all you need to store in topic views is user_id, date, topic_id ⌠you can do away with ip and a slew of anonymous records. It also assists with import.
I do support changing this.
Do you really want to get rid of anonymous views? I figured that maybe you keep whatever you id withâŚuserid/IP plus a date and a view counter. When you get a view after 8 hours (or whatever), the view counter increments and you update the date to now().
I guess maybe that turns a COUNT() into a SUM(), but I havenât studied the schema or anythingâŚstill, might result in lower DB I/O for performance than a count.
No, not at all, just avoid storing this info, we can use redis to ensure we only do 1 insert per IP per 8 hours. Without needing to store the IP.
There is also Redis new data structure: the HyperLogLog - <antirez> if we want to approximate âunique viewsâ
I really like the idea of calling it âreadersâ, because views just doesnât accurately portray what it represents.
Also, I like the idea because it shows DC is innovating, reimagining forum software.
The question is, is âReadersâ more useful than âViewsâ? I think yes, and that itâs worth tracking both, but showing Readers to users. (More on why I think itâs worth tracking straight views as well when I post the mock-ups I promised in another thread.)
Yes, either rename the existing column or change the way views are counted.
Showing the âViewersâ has its merits, but personally I think the information isnât useful enough on the topic level. It would be more interesting to see who read each post, but that raises lots of privacy concernsâŚ
So, Iâd go with a better algorithm for counting views. The 8 hours solution sounds good to me, seems to be better for performance and doesnât discriminate between logged-in and anonymous users.
Thatâs a good question. Views from known bots shouldnât be counted.
Personally, it seems like wasted computational power to try to filter out views from bots with very little benefit.
Additionally, I would say the time limit for counting a new view from either a logged in user or an IP address should reset as soon as thereâs a new post in the topic.
Just wondering. Will the algorithm for counting views be changed in the near future?
I think the longer this stays the way it is now, the harder it gets to change it.
Changing the way views are counted seems like a âbreaking changeâ to me, since you canât compare old view counts to new ones anymore. Or is there enough data available to recalculate the old view counts if necessary?
I read this thread with great interest because I have found that on my forum, âviewsâ is being interpreted by observers as âPage Viewsâ and on that basis, the forum looks considerably quieter than it actually is. That misperception has a detrimental knock-on effect, when trying to bring in new visitors - Not much going on here, look at the (page) views.
thanks to @michaeld we now have âReadersâ instead of âViewsâ sitting a lot more comfortably in the column heading, mouseover text and thread summary.
With no chance of confusion with page views now, I hope new visitors will also pick up on the number of readers using the site and perceive us better. Whether my feeling translates into an improved level of input or flow of traffic? I will report back when there is a better chance to see a pattern.
Reader carries a bunch of baggage though, one could expect âreadersâ to mean people who read the topic, which is not what views means, they could have simply visited and shut down the browser.
In that case âVisitorsâ might be a better fit.
@mcwumbly We are caught in a cage of words. True synonyms are hard to come by
If you want to reflect discourse, isnât there a case for not counting that sort of milli-second frivolous visitor?
What about people who read 4 out of 100 posts? this is real murky ground
This should still be the plan.
I checked the topic_view_item.rb
, and it looks like itâs still one view per IP ever? Personally, I donât mind, as long as I correctly understand what a âviewâ means, so that I donât misread/misanalyze the stats.