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

Reduce likelihood of making mistakes in sound moderation and make it easier to correct mistakes #1777

Open
qubodup opened this issue Jun 8, 2024 · 0 comments

Comments

@qubodup
Copy link

qubodup commented Jun 8, 2024

I have accidentally approved and deleted sounds before. I have seen sounds by other moderators where the ticket message indicated intent of deletion or at least deferral but the sound was published instead.

Some mistakes are extreme and impossible to fix (unintended sound deletion), others potentially require very high effort to fix (you approved a sound that clearly required deletion. You don't remember the username. You have to 1. wait for the index to update and 2. Browse through recent sounds to find the problem. The search ironically becomes more tedious the more work the moderator has already volunteered in the same timeframe (approved other sounds).

Cause:

  • Human error (possible to reduce, impossible to avoid)
  • Unbalanced visual communication and form layout of moderator actions

Solutions/improvement:

  • In any form that allows deletion and whitelisting, set apart deletion and whitelisting visually. For example via styling deletion with a red button/background and whitelisting with pink (don't use white, it's not visible in default style). Example animation from freesound-mod_queue_optimizer userstyle below (press play in top right corner):

freesound_mod_queue_optimizer-preview

  • Change the text of the submit button depending on the action chosen. Adding multiple buttons is not a good solution, as accidental clicks happen:

delete approve

  • In any form that allows deletion and whitelisting, an additional confirmation pop-up should be used to confirm the decision. Text must be short. Standard JS confirm() function with brief message suggested. Modearation queue: "Do you really want to delete the selected sounds?" and "Do you really want to whitelist the selected sounds' users?". Ticket page: "Do you really want to delete this sound?" and "Do you really want to whitelist this sound's user?" (single quotes might need escaping). It is important to test if pressing 'cancel' will actually stop the deletion and if 'ok' will actually delete. Confirm on ticket page mockup:

delete ticket warning

  • Create a per-moderator history list of all recent actions per sound. Suggested pseudocode limit with first item being index 0: if (sound_position_from_most_recent > 999 AND 30 days. If you moderated 1,000 sounds in the past 8 years, all 1,000 sounds remain in the list. If you moderated 8,795 sounds in the past 30 days, all 8,795 are in the list. On day 31, only the most recent 1,000 moderation steps remain. This list must track the moderation date of each sound and use it for sorting and cleanup. Not sure the list requires images/playback ability. Perhaps admins would want to be able to see these lists as well, however since it only tracks the latest action per sound (if moderator 1. approves - 2. deletes - 3. comments, only "commented" will show). To consider: 1. What if user comments/does action (should still work). 2. What if sound gets deleted by user or mod or other mod? (should still work) 3. What if sound gets reassigned to other mod (should still be here (as well in the new mod's list) and show this moderator's latest action):

possible location of history page in moderation navigation
page mockup but missing links

Title User Upload date Action date Action Status Ticket
Cartoon laugh supersoundtestuser 2024-03-30 2024-06-01 Delete Deleted # 999
Horse user99 2020-03-30 2024-05-15 Approve Approved # 444
A splash auser 2023-12-30 2024-04-05 Defer Deferred # 944
             
This links to the sound page This either opens the modal that lists pending user sounds or links to the user page for simplicity. Or has also an icon that does the modal while the name links. Keep it, why not. Most recent action date Most recent action title Status title This links to the ticket page. The number is not important and could be replaced by icon with ‘title=”id”’ attribute
  • Instead of deleting sounds, put them in a 'removed' list that behaves publicly as if deleted but allow restoration by admins. At least for 3-12 months.

Perhaps the individual suggestions should be split into tickets if accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant