[Feature] Administrative section for blacklisting domains from link fields

[echo6ix]

Is your feature request related to a problem? Please describe. It is a recurring issue that unwanted domains are added to the link field of scenes, such as JavLibrary. While using crowdsourcing to filter bad data or guideline violations is part of the ethos of StashDB, automating as much as possible improves efficiency and help to improve the quality of data and overall user experience.

Describe the solution you'd like Integrate a blacklist mechanism that administrators/moderators would have the ability to control by prevent specific domains from being submitted to the link fields of scenes, studios, performers, etc.

Key features would be:

• Blacklist management. The proposed feature should include a dedicated interface for managing the blacklist, allowing administrators and moderators to easily add, remove, and update unwanted domain entries.
• Granular blacklist management permissions. To accommodate any different levels of administrative access, either now or in the future, it is essential to implement a permission system. This would enable specific users, such as possible "global moderators", to have the authority to manage the blacklist.
• Clear error message notification to user. Let the submitter know why their submission will not submit. Give them an informative message that the particular domain is blacklisted.

[vt-idiot]

Aw, but then I won't be able to shout

# JAVLibrary is not a studio link

on my edits

[AdultSun]

Your recent issue #656 reminded me of this one. It would be useful to have a mod/admin controlled blacklist for fields and objects other than links as well, specifically to block the submission of banned studios and performers or unwanted names/aliases.

The one concern for me with maintaining a blacklist of suspected legal names for performers though is security. We wouldn't want to have a single list of those names vulnerable to a bad actor hacking our system to steal them, so we would have to be very confident in our security around that feature before I'd feel comfortable using it for sensitive information like that.