RE: Give Maintainer Permissions to delete their own nodes?

Besides the technical issue (orphaning possible replies), what's to stop someone from making an inflammatory comment, allowing people to reply, and then deleting it? Granted, that's a contrived example, but it could happen.

I suggest that the need to *delete* a node is rare enough that making an appeal at Editor Requests will take care of it. If not, perhaps an automatic means to take care of the duplicate/blank nodes issue will present itself.

As for editing nodes after the fact, I see that some monks put an Update: heading followed by the new text. Works for me.

Comment on RE: Give Maintainer Permissions to delete their own nodes?

Replies are listed 'Best First'.
Deleting isn't really more powerful than editing. by kudra (Vicar) on Jun 11, 2000 at 10:50 UTC
1.0 Since there's nothing at the moment to stop someone from making an inflammatory comment then editing it to a blank post or a 'sorry, duplicate, please delete', I don't think that bein able to remove the post would add any power in that way. It is nice when people use Update:, but nothing keeps them from not doing it (if this ever became a problem, perhaps version numbers could be automatically included,as demonstrated in this post). If duplicate and blank nodes couldn't be posted, I agree that it would be rare for someone to want to delete a post. I can't think of an example this morning. However, one way to handle it if it were needed, which wouldn't break threads, would be to simply change the text to "This node has been deleted by <author\|admin> [because <reason>]", then add a note next to the title that says Deleted. The body text wouldn't need to show unless the node had been specifically selected.	[reply]

Replies are listed 'Best First'.

Deleting isn't really more powerful than editing.
by kudra (Vicar) on Jun 11, 2000 at 10:50 UTC

Since there's nothing at the moment to stop someone from making an inflammatory comment then editing it to a blank post or a 'sorry, duplicate, please delete', I don't think that bein able to remove the post would add any power in that way. It is nice when people use Update:, but nothing keeps them from not doing it (if this ever became a problem, perhaps version numbers could be automatically included,as demonstrated in this post).

If duplicate and blank nodes couldn't be posted, I agree that it would be rare for someone to want to delete a post. I can't think of an example this morning. However, one way to handle it if it were needed, which wouldn't break threads, would be to simply change the text to "This node has been deleted by <author|admin> [because <reason>]", then add a note next to the title that says Deleted. The body text wouldn't need to show unless the node had been specifically selected.

[reply]