It is really easy to add moderation, as has been suggested, but I imagine that there is some hesitation in terms of limiting productivity and frustrating developers who have to wait on a second set of eyes. Even if all participants understand and don't take it personally, it can still be annoying to:
a) be the person who has to wait a day or two for content to go live because their moderator is out sick and the back-up moderator is in a meeting.
or
b) be the person who gets interrupted every hour or so from a project to click "approve".
Sometimes even technology calls for some of the suggested bureaucracy and needs to accept the headaches it comes with, and I think there are definitely smart ways of keeping the annoyances like the ones I mentioned to a minimum.
Having said all of that, bear in mind that this manager's actions probably reflect his termination. Or at the very least how it took it. Perhaps another non-technical administrative solution would be to remove system access privileges as soon as you know someone is in a compromised position.
Whether the person turned in their two-week notice or had just gotten the sack that morning, they should either have moderated-access or no access at all to anything that goes public or is mission critical.
Most developers work really hard to gain the trust of superiors allowing them to make things public or write data directly to critical systems. But that trust should come with a very immediate exit-policy clause.
Regarding LogiPik:
I've never used it, but I just tried their demo. I uploaded the following (randomly looking for "close up" on google:
http://www.ethereality.info/ethereality_website/paintings_drawings/new/portraits/elena_formal_portrait/closeup-3.jpg
And it got back the following:
Evaluated as: porn Completed in 25
sec.
For me, that is too slow (for one picture) to get a false-positive, especially for $50 bucks American.