Idea to stop spamming on Roadmap - WPFolks — A community for the people who build on WordPress

It is great initiative that there is option to upvote the roadmap activity that you like. Also, there are badges if you upvote more requests. Both these thing together attracts lots of spammers. People upvote the requests without even reading the content or understanding it properly.
So, my suggestion is that, we would provide around 5-10 upvote limit to each user, users should be able to upvote only 5-10 requests at a time. Once task is published, their upvote credit will increase again. users should also be able to remove upvote from one task and assign to another if they don’t have any credits left.

Gautam Garg 3 weeks ago

One more suggestion, we should not allow user to upvote after code is already shipped.

Reply
Krupal Panchal 3 weeks ago

It’s a good suggestion @gautammkgarg

Also, the system should not allow ticket authors to upvote their own tickets, as this can lead to unfair ranking and misuse of the voting system.

Additionally, we can introduce a spam-detection algorithm to identify suspicious or fraudulent upvote activity. If the system detects spam behavior such as multiple upvotes from fake accounts, repeated voting patterns, bot activity, or unusual voting spikes, those spam upvotes should automatically be removed by the system.

Some additional anti-spam improvements that could help:
– Limit the number of upvotes a user can make within a certain time period.
– Detect and flag newly created accounts that only perform voting actions.
– Temporarily suspend voting privileges for accounts involved in suspicious activity.

Reply