Requested feature overview description.
If user is being linked directly on the post page, apply the blacklist on the image on the page as well.

This is normal behavior on other websites with explicit content blocks or similar blacklisting features. However instead of blocking the whole page, simply changing image into Blacklisted (similar to how deleted posts have image replaced with Deleted) should suffice.

Why would it be useful?
Many users do use blacklist, but getting directly linked to post page bypasses that completely. They are now seeing content they have blacklisted, nullifying the blacklist in this context.

What part(s) of the site page(s) are affected?

• Post pages.

I second this. Recently I've used the random page feature a bunch and keep stumbling across content I strongly dislike due to the blacklist getting bypassed.

Since the blacklist is applied client-side, would this mean that, technically, any post page would deliver the client a blank page and rely on javascript to reveal the image? Otherwise, could a person sent to a blacklisted post see the content before the blacklist was applied?

ikdind said:
Since the blacklist is applied client-side, would this mean that, technically, any post page would deliver the client a blank page and rely on javascript to reveal the image? Otherwise, could a person sent to a blacklisted post see the content before the blacklist was applied?

The option to block blacklisted post images could be made opt-in. JavaScript is already needed to make the blacklist work in the first place. All you lose is the ability to see an image loading, but you could have a click to reveal override.