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.
"User Profile" should be more informative.
I think the current information in a user profile is very limited . In my opinion, the following information should be added:
Visible to all users
-
The number of questions and answers
-
The number of helpful flags, posts edited by the user, and people reached
-
Tags involved by the user's activities together with associated statistics
-
Last seen
-
How long the user has been a member of the community
Visibe to the account holder
- detailed voting information
Why is knowing such information useful?
In my opinion, to improve the community performance, we need to examine how the community members contribute in their membership duration.
For example, if we see that many new users are willing more to asking questions, we may need set some policies or rules to encourage them to contribute answering posts.
Another example, if we see that many old users are not willing to flag inappropriate posts, we may need to improve flagging policy.
Another example, it may be useful to examine why many users occasionally contribute to a community.
Another example, if we know that the number of "people reached" is high enough for some users, we can conclude that they may be interested enough to contribute to others' posts.
Finally, I think knowing the last information mentioned above, "visible to the account holder", is very helpful for any user; I think it is clear enough and does not need more explanation.
> The number of /.../ posts edited by the user This information is already basically available. Fair enough, it's not …
4y ago
> The number of /.../ people reached I disagree that this would be a useful piece of information. Yes, I know that …
4y ago
There is already a Q Should we have "Last seen" times? which nobody has chosen to discuss for about a month and for feat …
4y ago
3 answers
The number of /.../ people reached
I disagree that this would be a useful piece of information.
Yes, I know that Some Other Q&A network displays such a number; relatively prominently, even.
I have always considered it mostly a gimmick, because quite frankly, it doesn't really tell you anything; especially, anything in my opinion particularly useful. And even if it did, it's not actionable; there's really nothing you can do directly to influence it either way.
It can give you a very rough idea of how many visits there have been to pages where you have either the question or an answer (while telling you nothing about which of those it is, or whether that traffic is spread out evenly or focused on a few of your contributions), but that tells you nothing at all about the in my opinion much more interesting metric: how useful was your contribution to them?
The latter of which, unfortunately, while actionable to some degree, probably borders on the impossible to measure directly. It therefore has to be measured indirectly, for example through votes.
So if anything, I personally would be far more interested in a more detailed vote breakdown, both votes given and votes received.
The number of /.../ posts edited by the user
This information is already basically available. Fair enough, it's not the number of posts edited, but the number of edits made.
If you open a user's profile, then go to Activity, there are aggregate counts for posts, comments and edits available in the header. This does seem to suffer from the Initial revision issue, but you can subtract the number of posts from the number of edits to get pretty close to the number of actual edits.
Unfortunately it looks like closing questions also counts as an edit, but then on the other hand, if a significant amount of a user's activity is to close posts, maybe they are here for the wrong reasons to begin with...
0 comment threads
There is already a Q Should we have "Last seen" times? which nobody has chosen to discuss for about a month and for feature requests I would prefer each to be dealt with individually. Also, for all feature requests I would prefer that the request specify why a proposal might be a good idea.
In general, I am not in favour of this batch of feature requests at this time because in my opinion there are higher priorities.
1 comment thread