Hide proposals with less than x vote weight

[auryn-macmillan]

Currently, Snapshot spaces can be prone to SPAM / low-quality proposals.

As part of GIP-77, we would like to add a setting to Snapshot which allows a space to define a threshold of votes that must be reached, along with a time period in which the votes must be cast, for a newly created proposal before it will be displayed in the space's main view (and considered a valid proposal).

This means that proposal authors must share their proposal directly with a critical mass of stakeholders before it shows up in the default view on the space.

The filter settings should be something like this:

"filters": {
  "threshold": "1000",
  "options": [0,2],
  "expiration": 172800
}

Where:

• threshold is the number of votes that a proposal must receive before it shows up in list of proposals and before any notifications are sent via bots.
• options is an array of the the vote option indexes that will count towards the filter threshold. If none are provided, any vote counts.
• expiration is the amount of time, in seconds from the time it is first published, that a proposal has to reach the threshold. If a proposal fails to reach the defined threshold before this timestamp, it is considered invalid and will never show in the default view.

[samuveth]

Hi @auryn-macmillan, after reviewing your proposal, I've identified some potential issues and would like to suggest alternative solutions to address them:

Potential issues

1. Increased complexity: The added threshold and time limit could make the platform more difficult to understand and navigate, potentially deterring users from participating.
2. Barrier to entry: The threshold requirement could create a barrier for legitimate proposals from users with limited access to large amount of holders and stifling inclusion.
3. Vote collusion: Users might coordinate with others to vote for their proposals just to meet the threshold, leading to low-quality proposals being displayed.

Proposed Alternatives

To address these concerns while still managing spam and low-quality proposals, we suggest the following alternative solutions:

1. Implement a stricter default filter on the space proposals page. For example, show only Core member proposals by default but allow users to view all proposals by adjusting the filter settings.
2. Introduce an approval process for proposals. This can be combined with Alternative 1, where unapproved proposals are still visible when users adjust the default filter settings. This will ensure that only high-quality and relevant proposals are prominently displayed on the space.
3. Space admins could increase the overall minimum threshold for creating a proposal, rather than introducing a time limit and specific vote options.

I appreciate your input and encourage further discussion or any other suggestions you may have. Our goal is to create an efficient and fair proposal evaluation process that fosters innovation, diverse perspectives, and a positive user experience.