Prevent Spammy X Replies in CommunityOne
Summary
In CommunityOne Builders Help this announcement outlines strategies to prevent spammy X replies caused by members farming Twitter quests. It proposes pre-filtering X accounts for reply permissions, disabling reply rewards by default except for special roles, or granting reply rights after completing quests over several days. These options aim to protect project tweet engagement and reduce low-quality replies.
This is probably a web3 issue where some members are farming points and thus making a project tweet's reply look really bad. Clearly, there's no great way to resolve the issues, but here's some potential solutions
-
Pre-filter members:when they connect with their X, we will check their past weets and automatically give them permissions to reply if we think the account is in good standing.
Downside: (1) We will have to charge extra (cuz a lot more extra calls on our side) (2) Members can't earn their way to reply. -
By default, do not reward users for replies, so only retweet and like. Only allow this option for the special roles, where the server owner get to decide on who gets the roles.
Downside: too much work on the server owner side to maintain this. Also not sure how everyone feels about reducing the comment engagement by default, -
Another option is to automatically grant them the permissions to reply only after they complete a certain amount of Twitter Quests over a spam of X days, hoopefully they will get a chance to learn a bit about the project before starting to contribute.
