Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Should we display the number of views?
I personally like the idea of knowing how many people have viewed my posts. Even if it's only shown for the person who posted the question
I think we should, voting score is a poor indicator of how useful a post is because most visitors aren't going to sign u …
4y ago
View counts are a measure of the importance of a post to the site. A question that's viewed a lot should be prioritized …
1y ago
soft no1 Codidact is already wasting a lot of storage space in the edits history2 and who knows what else, let's plea …
4y ago
3 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I think we should, voting score is a poor indicator of how useful a post is because most visitors aren't going to sign up and vote.
Right now it's hard to tell how many people are reading the posts created here from a user or even a moderator standpoint how successful we are at getting people to read our content.
On the old sites, I would also use that as an indicator of what questions people thought were interesting and then see about writing similiar ones.
0 comment threads
View counts are a measure of the importance of a post to the site. A question that's viewed a lot should be prioritized by curators, because it's likely to be viewed proportionately often in the future. They need to have this information to act on it, so I'm in favour of displaying it.
It's especially important for curators to be able to check if a Q&A is "clickbait" - in particular, if the person asking used a title that refers to a common problem, but the question actually describes a different problem. On technical sites, titles that contain error messages are also especially likely to clickbait: an error message can generally only capture a proximate cause of a problem, but the most interesting questions are about ultimate causes.
0 comment threads
soft no1
Codidact is already wasting a lot of storage space in the edits history2 and who knows what else, let's please not request unnecessary space waster features until the not-for-profit is already set up and the cash flow is demonstrated sustainable.
1: Temporary.
2: By storing (for each edit) both the state-before and the state-after edit.
1 comment thread