I have seen this in the past, but it always seemed to be a matter of Safari caching things and not actually reloading the page. I loaded both of those pages, so theoretically, the view counts should’ve just gone up…
This could be a result of the server-side caching we added in recently. It shouldn’t affect you while you’re logged in, but maybe there’s something odd going on. I’ll investigate shortly and let you know what I find.
I see two problems.
Adding our own user based analytics gives problems of GDPR, cookies, etc. It gets blocked by adblockers, and the like. You do not get very useful information.
Having write.as server based analytics provides for better and easier to anonymise analytics.
So we need @matt on board, who has hinted in the past he’s not interested to improve the server side, non javascript based analytics.
It would be good to have a clear roadmap, so we don’t need to keep bugging Matt for recurring problems and expected improvements, and know where we stand?
I just sent out an update that should fix this! As long as you’re logged in, your browser will no longer cache the page, so you should always see the latest view counts. Note that you may need to do one last hard refresh (Ctrl+Shift+R) for any pages you’ve previously checked on, but then you won’t have to do that anymore going forward.
Also, for anyone looking extra closely, note that there may still be a ~60 second delay between a hit on your site and the view counter updating. This is due to the way we batch view counts across the system for all users.
Thank you matt, but known crawlers, such as the archive.org, are still being counted as individual page counts. There must be something which can be done other then coding against the internet archive?