Comment/Post Deletion Notification
Short, concise description of the idea
Similar to the existing new comment/post subscription, this would send a notification upon a post or comment being deleted. This should only be available to community maintainers or moderators.
Full description of the idea
A community maintainer would subscribe to "notify me when anyone deletes a post from this community" or "notify me when anyone deletes a comment from this post". They would then receive a notification when someone deleted something that they were subscribed to. (If the suggestion for maintainer subscription to all comments in their community is implemented, this could be expanded to include a subscription to all deleted comments on all posts in the community, with the ability to stop tracking deletions on any given post without affecting the auto-subscribe to post/comment deletions on new posts.) Another refinement would be to subscribe to deletions of content by or deletions made by any given member of the community.
This is superficially similar to a rejected suggestion about notification for the user upon maintainer deletion, but this would work the other way around: notifying the maintainer when a user deleted content from a community that the maintainer manages.
Since the potential for stalking using this feature would be incredible if it were available to all users in all situations, the feature would only be available to community maintainers in their communities, thus restricting the feature to a narrower and legitimate application.
The notification would contain the name and IP address (if logging is enabled) of the user who posted the item, a link to the entry the comment was in (if applicable), the subject and text of the deleted comment or entry, the timestamp of the post or comment, and the username, IP address (if enabled) of the deleter, and the time of deletion. This level of detail would enable maintainers to quickly spot which deletions were merely people correcting their own typo, which deletions were done by other maintainers, and which deletions were by the owner of the post deleting someone else's comments.
- Parallels the subscription to the creation of posts and comments.
- Increase ease of maintaining high-traffic communities.
- A number of communities have rules against deleting posts, or deleting comments from other users simply because they expressed a differing opinion. This would make it easier for maintainers to see when this is happening. (suggestions could have used this feature in the recent past.)
- Fighting trolls and flamewars. Posting and deleting comments is a classic troll tactic.
- Maintainers would potentially have a copy of a comment that was deleted against the community's rules, and they could forward that copy to the user who posted it.
- Maintainers could see the content of a deleted comment or post in case it was something that required action on their part.
- Maintainers and people subscribed to posts and comments already do get to see comments and posts that have been deleted, after they have been deleted, through the e-mail notification system, if they have subscribed.
An ordered list of problems/issues involved
- People might not like it.
- People might want it for comments in their own personal journals or their comments that they have made in communities or other people's journals.
- Currently, comments and posts that are deleted are deleted right then and there; there is nothing stored. Implementing this might require changing that.
- Might not be available in the notifications inbox; might be an e-mail only feature, or might require significant change to support being used in the notifications inbox. (Since deleted items are not stored and not displayed in notifications mailbox.)
- There might be copyright issues with LiveJournal storing any post or comment content post-deletion.
- Post-and-delete as a method of passing private messages would be less secure than ever (though it was rendered completely insecure with the advent of comment subscriptions).
- Misuse of this could lead to drama.
- This could be used to spam a maintainer by repeatedly posting and deleting.
An organized list, or a few short paragraphs detailing suggestions for implementation
- Create an event upon deletion, if there isn't already one.
- Capture the necessary information. (Store if necessary.)
- Enable subscription to this event.
- Check for maintainership in the community before allowing subscription (or offering subscription).