This is a proposal for a new feature that's been lingering on my mind for some time regarding how we handle content from banned artists.
As it stands, the way that banning content works is that the image itself is not viewable by member-level users. Searching for banned content will not work unless you are at least Gold+.
However, if the image is only to be hidden and the search tags are still available, then what if we, instead of just having banned posts be completely hidden from those users being able to search them, just leave some sort of a placeholder/thumbnail image indicating that that content is banned? That way these posts are searchable by all users (not just Gold+) and still easy to find, but we're sidestepping the fact that we're 'hosting' their content to all users that browse this site. These posts will still be accessible from the source link just as long as the source link continues to remain live.
The longer backstory for this is that I noticed that Provence went and uploaded post #2655103, and this got me thinking a little bit -- as builders with unrestricted uploads and approval privileges, how acceptable would it be to upload content from banned artists that are well tagged, and then are immediately banned/hidden right after uploading? Of course, this method of uploading would really only apply to users that can ban posts, users with approval privileges. But I think there could also be a way for users with unrestricted uploads (or just Builders in general) to upload 'banned' content through this method. Say, if there were a option box/checkmark on the upload page to mark their upload as banned content.
Banned content can be instantly marked through the bookmarklet, duly noted.
In summary, since images are banned but the tags/other relevant content are not purged with it, this feature request is for banned posts to be indexed and searchable by member-level users (through displaying placeholders/thumbnails) while leaving the original image unavailable. So let's discuss it.
I'll ping some users related to the codebase since this is also quite relevant to them @evazion @BrokenEagle98
EDIT: For clarity
Updated