Beatmapset discussion upvotes should be limited/weighted based on overall modding contributions

[Ephemeralis]

Currently, as Kroytz has demonstrated (and many people in the developmental phases of moddingv2/beatmapdiscussions have pointed out), beatmapset discussion upvotes can be readily abused by small parties of participating users in order to artificially inflate the amount of kudosu awarded for a particular modding contribution.

This can be addressed in a few ways:

• Upvotes could only be applied by users with a certain amount of established modding experience. This is crystallized via kudosu in the system currently, meaning that you could require a basic minimum of perhaps a week or two's dedicated contribution (100-200 kudosu) in order to allow upvoting.
• Upvotes could have their progress towards bonus kudosu scaled based on the level of the user's overall contribution. Essentially, if someone with a lot of kudosu upvotes your map, it can be taken to mean more, and thus increment progression towards bonus kudosu more appropriately

Otherwise, any other solution that appropriately limits the means for average users with no modding experience to inflate the values of others would work, these two are just the most immediately obvious ones I can think of.

[cl8n]

both of these sound like good ideas to me. goes along the lines of the idea to eventually™ scale people's privileges in the system based on their experience like stackexchange or w/e

another issue with Kroytz's thing was that lots of very similar mods were able to receive kudosu individually (NC mods, volume changes, etc). I think it would be helpful to have a feature in modding discussions for referencing multiple timestamps/objects from one core issue, that way they could appear on the timeline as expected but not count as tons of unrelated suggestions that each can be upvoted separately. currently, people are encouraged to make posts under the General tab for this case, which kinda defeats the point of having a timeline.

[NoffyNoffeh]

For reference,
#1698
#2040
also relate back to this problem and propose different solutions

The mapper should always be able to upvote similar to what is mentioned in Naxess' post which I linked first. This would work best if combined with #2165 so that guest difficulty creators could also upvote helpful posts on their difficulties.

For users besides the mapper of a set, the ability to upvote coming with contribution sounds like a good idea. However, this would need to be in a way that the power can be easily removed from a user if needed by moderators, which may be difficult if the ability is based solely off of kudosu count and that should be accounted for in a possible new system.

[peppy]

I think it's best we develop a new modding score metric to replace kudosu as part of this move, and introduce a tier where upvoting becomes a possibility.

[peppy]

Moving back to candidate as this is too vague to be implemented just yet. Of note, we are focussing on the modding discussion system this month and will likely resolve a part of what is mentioned here.