It is for profile views though. I think it would just take too much extra memory unnecessarily (just for the sake of unique views) if we were to keep track of every single user that's visited every single thread.
Count going up by 2 though is a bug that was fixed recently
when I new a rewards ,and set Amount of times reward is claimable to 1 when user post count >=10 ,this rule can be trigger twice ,When you post several times, including twice as long to meet more than 10 Posts.
I view the code about rewards ,and found the issue in src/rewards/index.js 93 line
@zenkamal @a_5mith This sounds like it's due the new way we store post bookmarks.
Before, we stored the pid (e.g. 2341)
Now, we store the post index (e.g. 5)
The bookmark only updates if the current post # is > than the bookmarked post #
Unfortunately, 5 will never be greater than 2341, so the bookmark never goes away.
The old bookmark is basically trying to load the 2341th post in the topic, which doesn't exist. You can clear the bookmark by clicking the "x" at the top right of the notification alert, then that topic should be fixed.
Noticed today that when viewing a thread, sometimes the post count position doesn't load in properly like this postcount error.png It will display fine once you click it so it's not causing any functionality problems it;s just a tad odd.
It only seems to happen when clicking a link through the unread section, if I load a thread by browsing the actual forum it seems to load in fine every time.