Improvements to community flagging of explicit photos #50

Open
opened 2024-10-01 23:15:23 +00:00 by noah · 0 comments
Owner

Currently:

  • Users on the gallery can flag a non-explicit picture as needing to be marked explicit.
  • The picture is immediately marked as explicit, and an admin report is generated for visibility to admins.
  • But nothing else happens (no notification sent to the owner of the picture), and if the owner notices their pic was marked explicit they're able to edit it and remove the explicit label which can go undetected (until their pic is flagged again, enough times that an admin notices seeing the same pic and checks the history on it to see that the owner has been fighting the flag).

Also: some users (especially new members who may not know better) tend to be the ones most likely to post a bunch of explicit pictures without correctly tagging them, and since they aren't notified in any way some of these users may obliviously continue to do so forever, creating more work on the rest of the community to keep flagging these pictures as they come in.

Some ideas how to improve it:

  1. ✔ Notify the owner of the photo when their pictures get flagged as explicit.
    • ✔ It should go on their Notifications page, showing the picture itself (similar to a like/comment notification) and say a community member has flagged it as explicit.
    • ✔ It should contain a short blurb of text explaining why a picture should be marked as explicit (erection, sexual content, etc.) with a link to more info.
  2. When a picture is flagged by the community, the database should remember this.
    • ✔ The photos table currently has a flagged boolean column which is not used for anything: flagged could be set to true when a photo is flagged as explicit by the community.
    • ✔ If a flagged=true picture is modified and the 'explicit' setting moves from true -> false, this should notify the admin with a report saying: "this flagged explicit photo was moved back to non-explicit" (for earlier detection if somebody fights the flag)
  3. A photo should be able to receive an admin's "blessing":
    • e.g.: a user flags a photo as Explicit, and an admin reviews it and decides it really did not need to be explicit: the admin can mark it non-explicit and "bless" it to prevent this same photo from being flagged again by the community.
    • On the admin reports page (when a pic is flagged by the community):
      • Show the picture itself in the report, blurred out and revealed on a click
      • Include handy in-line links so (in case of a false report and the flag was not warranted), the admin can mark it non-explicit and "bless" it in one go.
    • A blessed non-explicit picture will not show the prompt "Should this photo be marked as explicit?" beneath it anymore.
    • Should the "blessed" field be a boolean or have support for multiple states? Ideas for states could include:
      • Verified non-explicit (don't show users the prompt to flag it as explicit when it is not explicit)
      • Verified explicit (remove the owner's ability to remove the explicit flag)

Along with this, the photo upload page could use some tweaks to its wording to help make it more clear to users when they should check the 'explicit' box.

Currently: * Users on the gallery can flag a non-explicit picture as needing to be marked explicit. * The picture is immediately marked as explicit, and an admin report is generated for visibility to admins. * But nothing else happens (no notification sent to the owner of the picture), _and_ if the owner notices their pic was marked explicit they're able to edit it and remove the explicit label which can go undetected (until their pic is flagged again, enough times that an admin notices seeing the same pic and checks the history on it to see that the owner has been fighting the flag). Also: some users (especially new members who may not know better) tend to be the ones most likely to post a bunch of explicit pictures without correctly tagging them, and since they aren't notified in any way some of these users may obliviously continue to do so forever, creating more work on the rest of the community to keep flagging these pictures as they come in. Some ideas how to improve it: 1. ✔ Notify the owner of the photo when their pictures get flagged as explicit. * ✔ It should go on their Notifications page, showing the picture itself (similar to a like/comment notification) and say a community member has flagged it as explicit. * ✔ It should contain a short blurb of text explaining why a picture should be marked as explicit (erection, sexual content, etc.) with a link to more info. 2. When a picture _is_ flagged by the community, the database should remember this. * ✔ The photos table currently has a `flagged` boolean column which is not used for anything: flagged could be set to true when a photo is flagged as explicit by the community. * ✔ If a flagged=true picture is modified and the 'explicit' setting moves from true -> false, **this should notify the admin** with a report saying: "this flagged explicit photo was moved back to non-explicit" (for earlier detection if somebody fights the flag) 3. A photo should be able to receive an admin's "blessing": * e.g.: a user flags a photo as Explicit, and an admin reviews it and decides it really did not need to be explicit: the admin can mark it non-explicit _and_ "bless" it to prevent this same photo from being flagged again by the community. * On the admin reports page (when a pic is flagged by the community): * Show the picture itself in the report, blurred out and revealed on a click * Include handy in-line links so (in case of a false report and the flag was not warranted), the admin can mark it non-explicit and "bless" it in one go. * A blessed non-explicit picture will not show the prompt "Should this photo be marked as explicit?" beneath it anymore. * Should the "blessed" field be a boolean or have support for multiple states? Ideas for states could include: * Verified non-explicit (don't show users the prompt to flag it as explicit when it is not explicit) * Verified explicit (remove the owner's ability to remove the explicit flag) Along with this, the photo upload page could use some tweaks to its wording to help make it more clear to users _when_ they should check the 'explicit' box.
noah added the
enhancement
label 2024-10-01 23:15:23 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: nonshy/website#50
No description provided.