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.
Understanding how posts were possibly received by the community --- network wide
I would always claim that anonymous upvoting and downvoting are a crappy quality assurance method causing more harm than good in the long run due to unbased (or well based) accumulated hostility and would generally not even use it but if it is the only method to get communal feedback on a user's posts I would reluctantly use it.
It's a bit frustrating for me to check every Codidact website to learn how a given post of mine (or of another user) was received by the community.
I'd prefer to have visit some single webpage that will show two tables per network website (one for questions and one for answers) with any post I have published in any website in the network (probably it will include a pager in case there are too many posts per table);
From there, to easily know how many upvotes and upvotes each post got (if at all) and on the way, to know what is my "reputation points number" on the relevant network website.
1 answer
I think what you're asking for is (1) better information about votes you're receiving, so you know which posts are being up- or down-voted, and (2) for that information to be available in one place.
For the first, we do want to provide this information on the user profile page. You should be able to see information on recent votes. Speaking for myself, if one of my posts is getting downvoted I want to know so I can try to improve it, and if one of my older posts is suddenly getting a lot of new attention in either direction, I want to look at it again to see if I should try to improve it. Knowing how our contributions are being received is more valuable with timing information than just seeing totals. The reputation number is the only source of information about changes right now, and it doesn't tell you where the activity happened. That's a known deficiency, and one we plan to address.
For the second, having the changes from all communities in one place, we haven't talked about that. We do need to add a network profile, a place where all your individual accounts are linked and maybe a place to record network-wide preferences, but we haven't talked about other uses for that profile yet. I think our approach is going to be to first get this information on existing user profiles (one community at a time) and then figure out what else is feasible. (By the way, our team lead thinks the issue I linked here doesn't require a lot of Ruby knowledge -- if anyone's interested in trying it, please comment on the GitHub issue.)
1 comment thread