skidmark said:But my main point is that even if you are pragmatic, it also makes sense to be more heavy-handed about it, in the sense of actually advertising that you don't want people talking about it. If you just make it go away, people might wander onto the forums and not see it there and bring it up again.
^^^
What he said.
I also want to add something else. Deletion or modification of posts should come with a good explanation, even more so, if whole threads are deleted. Removing someone's written opinion does not sit very well with some people - people like me, who grew up suffering from despotism and censorship of a Communist dictatorship (East Germany in my case). They too had a predilection for removing unwanted opinions (ok they usually removed the person who voiced it too, I give you that).
If you have reason to modify a thread because a Lawyer growls at you, why not notify the authors of offending post, giving them - let's say 24h - to modify the problematic posts and why not publish what those lawyers threaten you with? If you delete a 200 posts thread because of 10 offending posts, you violate the right of free speech of up to 190 people without much of an explanation.
That feels too Mao Zedong for many people's comfort.
As for the technical reasons behind the deletion of the Kimmage thread. Do you guys not have database admins? How about asking their opinion before you do something as drastic as deleting a user per his own request? The User-Id is bound to be used as a foreign key in many tables. Deleting a user would therefore either orphan a lot of table entries or simply cause their deletion as well, which in turn causes removal of much more data than was supposed to.
How about renaming the user to "deleted user#<userid>" and setting all his posts to "--- deleted by user request ---". In the ideal case that's two UPDATE and a COMMIT statement and the work of two minutes. That way you don't accidentally delete other people's post. (see Mao Zedong)
