Consider adding a 'report' button/option to bounties.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 776
- PR merge metrics
- No merged PRs in 30d
Description
As gitcoin allows anyone to become a bounty funder and post bounties without verification it often happens that bounties appear which are either incomplete, lack necessary information, or are just spam -- often posted by immature users of the web -- or much worse, are simply scams. Those are not only a waste of hunters' time, but also spark confusion, decreasing the accessibility and attractiveness of the service to new users, as well as possible investors.
I suggest adding an option to report such 'misbounties', be it with a button or any other ui element.
That would then notify the appropriate people who would decide if a reported bounty should be removed, and if it can be improved upon point the poster to the appropriate resources describing how they can do so. The removal may also be decided by the number of reports, which would decrease the amount of trusted verification needed, although the exact model of responding to reports is a minor issue. Such removed bounties shall remain on public display under a "removed" category, for the gitcoin service to remain transparent and trustworthy. Thus, no removal really happens - the bounties are simply 'tagged' as incorrect.
This issue also seems to be covered, perhaps somewhat inprecisely, in [your terms of service](https://gitcoin.co/legal/terms), section 5:
> As a Poster, you agree that: (a) you will interact with Hunters in a professional and courteous manner, and accurately describe your Task
With such improper bounties there often, of course, is no real 'task' to be done.
## Examples:
https://gitcoin.co/issue/29288
Contributor guide
Research direction
No implementation files or tests are named. Start by reviewing the bounty UI and the example bounty at gitcoin.co/issue/29288, then read the linked terms-of-service section to understand the reporting context. Done would require an agreed reporting workflow, moderation outcome, and visible handling for reported bounties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100