Asklemmy

The point of blocking is to cause things to be invisible to the default view.

If the blocked material is put in users' face so they know it's blocked, that misses the point of blocking it.

Mod logs and published block lists are a great way of allowing users who are concerned about overblocking to investigate ... without failing at the whole endeavor by sending every user a copy of all the horse porn & Nazi spam that got blocked.

When I ran spam filtering for an institutional email server about 20 years ago, I made the "mod logs" (or rather, SMTP envelope data of blocked messages) available to users; but they had to go to a web page to see what messages had been blocked; and the content was not visible (since the mail server had never accepted it). I wrote that code so that my users could tell me if the spam blocking I'd configured was mistakenly blocking mail they wanted to receive.

(The users were scientists & engineers. They could read email headers. If they wanted to.)

But the point of blocking the horse porn spam and Nazi froth is lost if the users have to see it anyway so they know it's blocked.

Horse porn is not a made-up example, by the way. There was an email spammer named Jeremy Jaynes, who was in the habit of sending spam promoting bestiality porn. When he was arrested, suddenly the users on the email server I was running stopped complaining to me about horse porn.