We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-05-14 15:09:11 +0200 |
A short time ago I noticed inconsistent counting of site views. View count does not rise as long as you call your own request and there are no answers, otherwise each time you call a site the counter steps up, even if you visit your own requests, and even if you only refresh the site. Try for yourself.
I think that was different before, so that view count was a reliable indicator of how many people have seen a request and not of how often a site has been looked up (repeatedly). In case a request is only refreshed over and over again by a couple of visitors, this indicator gets completely irrelevant.
Is this by purpose or a bug?
2 | No.2 Revision |
A short time ago I noticed inconsistent counting of site views. View count does not rise as long as you call your own request and there are no answers, otherwise each time you call a site the counter steps up, even if you visit your own requests, and even if you only refresh the site. Try for yourself.
I think that was different before, so that view count was a reliable indicator of how many people have seen a request and not of how often a site has been looked up (repeatedly). In case a request is only refreshed over and over again by a couple of visitors, this indicator gets completely irrelevant.
Is this by purpose or a bug?
3 | No.3 Revision |
A short time ago I noticed inconsistent counting of site views. View count does not rise as long as you call your own request and there are no answers, otherwise each time you call a site the counter steps up, even if you visit your own requests, and even if you only refresh the site. Try for yourself.
I think that was different before, so that view count was a reliable indicator of how many people have seen a request and not of how often a site has been looked up (repeatedly). In case a request is only refreshed over and over again by a couple of visitors, this indicator gets completely irrelevant.
Is this by purpose or a bug?
4 | No.4 Revision |
A short time ago I noticed inconsistent counting of site views. View count does not rise as long as you call your own request and there are no answers, otherwise each time you call a site the counter steps up, even if you visit your own requests, and even if you only refresh the site. Try for yourself.
I think that was different before, so that view count was a reliable indicator of how many people have seen a request and not of how often a site has been looked up (repeatedly). In case a request is only refreshed over and over again by a couple of visitors, this indicator gets completely irrelevant.
Is this by purpose or purpose? IMO it is a bug?bug.
5 | No.5 Revision |
A short time ago I noticed inconsistent counting of site views. View count does not rise as long as you call your own request and there are no answers, otherwise each time you call a site the counter steps up, even if you visit your own requests, and even if you only refresh the site. Try for yourself.yourselves.
I think that was different before, so that view count was a reliable indicator of how many people have seen a request and not of how often a site has been looked up (repeatedly). In case a request is only refreshed over and over again by a couple of visitors, this indicator gets completely irrelevant.
Is this by purpose? IMO it is a bug.
6 | No.6 Revision |
A short time ago I noticed inconsistent counting of site views. View count does not rise as long as you call your own request and there are no answers, otherwise each time you call a site the counter steps up, even if you visit your own requests, and even if you only refresh the site. Try for yourselves.
I think that was different before, so that view count was a reliable indicator of how many people have seen a request and not of how often a site has been looked up (repeatedly). In case a request is only refreshed over and over again by a couple of visitors, this indicator gets completely irrelevant.
Is this by purpose? IMO it is a bug.
EDIT: The observed pattern is that only the last editor of the thread is not counted repeatedly. Everyone else is counted each time s/he visits the thread. So if someone creates a new answer, the non-counting "privilege" is transferred to him/her.