Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quality benchmark #837

Open
pinkforest opened this issue Jul 23, 2024 · 3 comments
Open

Quality benchmark #837

pinkforest opened this issue Jul 23, 2024 · 3 comments

Comments

@pinkforest
Copy link

pinkforest commented Jul 23, 2024

There are some requests that hurt everyone.

It would be great if there is some type of pressure to raise quality of submissions whilst not inpinging people's productivity.

It makes it harder to use the site given one user can effectively cause blockage (see the internal system) by the authority.

These blockages whilst illegal (maybe who knows) provide plausible deniability because one random person (or bot) did it.

Possible improvement options

  1. Crowd-source reviews on first time posters by trusted ambassadors

  2. Provide feedback via crowd-sourcing on first time posters from trusted ambassadors

  3. Feedback positive-only score e.g. people can give thumbs up (not thumbs down possible as it can end up "brigading")

@benrfairless
Copy link
Member

Hey @pinkforest

Would you be able to provide examples of low quality requests?

If you would prefer, feel free to email these through.

@pinkforest
Copy link
Author

pinkforest commented Aug 4, 2024

https://www.righttoknow.org.au/user/john_smith_22

It's also against the house rules - targeting one minority group - if not plain vilification - it doesn't just ask stuff

@benrfairless
Copy link
Member

I've been thinking about a possible way to address this without creating too much overhead on our volunteers.

We could consider immediately hiding anything that is reported to Administrators until we have time to review it. This would allow the request to proceed as normal, however would also reduce any harm by having the request public.

@benrfairless benrfairless self-assigned this Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants