You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
Some very special people like to mass vandalize tags, usually dozens or hundreds at a time. Often these go unnoticed for hours, or even days, until some unfortunate soul does a in innocent search for something "safe" and is met with definitely "unsafe" images.
Describe the solution you'd like
A hitman.
Describe alternatives you've considered
Staff can flag certain tags as "High Risk" or "Monitor Changes". Whenever a tag with this flag is removed or added from an image, a report is generated in a new, separate moderation queue, "T". A separate queue is desirable in order to highlight the problem (as it should be dealt with in a definite manner quickly) and not affect the normal Report queue (often filled with low priority or claimed tickets).
Reports can be generated per image affected by the monitored tag, or one single report per monitored tag per IP/user (as staff can then track tag changes made by that IP/user).
Staff can mass mark / tick reports as claimed / closed, as tag vandals often hit many multiples of images at once.
Additional context
None that wouldn't get this repo deleted.
The text was updated successfully, but these errors were encountered:
Problem:
Some very special people like to mass vandalize tags, usually dozens or hundreds at a time. Often these go unnoticed for hours, or even days, until some unfortunate soul does a in innocent search for something "safe" and is met with definitely "unsafe" images.
Describe the solution you'd like
A hitman.
Describe alternatives you've considered
Staff can flag certain tags as "High Risk" or "Monitor Changes". Whenever a tag with this flag is removed or added from an image, a report is generated in a new, separate moderation queue, "T". A separate queue is desirable in order to highlight the problem (as it should be dealt with in a definite manner quickly) and not affect the normal Report queue (often filled with low priority or claimed tickets).
Reports can be generated per image affected by the monitored tag, or one single report per monitored tag per IP/user (as staff can then track tag changes made by that IP/user).
Staff can mass mark / tick reports as claimed / closed, as tag vandals often hit many multiples of images at once.
Additional context
None that wouldn't get this repo deleted.
The text was updated successfully, but these errors were encountered: