IntersectMBO / IntersectMBO/govtool

Spam Prevention - Moderation

Open
#2,842 0 comments 0 reactions 2 assignees Claimed by @bosko-m View on GitHub
Nice to Have
Dominant language
HTML
Stars
21
Forks
29
Avg merge
2d 22h
Merged PRs (30d)
7

Description

In any moderation system, it's crucial to ensure that content and comments are linked to legitimate identities. Sybils—fraudulent identities—can disrupt messaging and lead to unintended outcomes, especially in automated moderation. While manual moderation is an option, it often lacks scalability. Here are some of my first thoughts:

**1. Weighted Flagging**: Assign a weight to each user's flag based on their stake, as each user identity is associated with a stake key. This approach minimizes the impact of cheaply created sybils, as their flags would carry little to no weight.

**2. Minimum Stake Requirement**: Additionally, require each user to maintain a minimum stake of, for example, 1 ADA in their wallet. While this will not entirely prevent spam, it increases the cost for spammers to create sybils, thereby reducing spam incidents and lessening the burden on other moderators.

Since the Proposal Discussion Forum (PDF) operates off-chain, spam prevention measures must be enforced at the backend. Frontend checks using browser wallets alone will likely not be sufficient.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.