Lots of words.....
A front end management system to hold onto deleted content until a second action can be performed doesn't do any good if a member knows that and remembers to delete it twice.
Front end deletion management is no where near as good as proper database backup management.
Edit history, I agree on that point. Much like IPC now has edit history, it would be nice to store at least the past couple revs of a post.
That problem can be alleviated by the addition of proper permissions management for super moderators, and even admins. Just like you're able to restrict exactly what each admin and admin group can do in the ACP, we should be able to control exactly what a super moderator is able to do and not do. In other words, someone should not automatically gain the ability to wipe all of the site's content from the database just because they are in a group with "super moderator" privileges.
Database backups, assuming you have them (you should, but that's for another topic), are very useful in case a significant amount of your site's content is deleted for whatever reason, but they are extremely cumbersome to restore little bits of "hard-deleted" data from. I had to use a few custom queries to restore all of a member's status updates from a database backup after someone figured out their password and deleted all of them from their account (that prompted me to start this feedback topic
to make status updates "hideable").
Digging out a 2+ GB .sql file from my backup server, importing it into MySQL so I can work with it, locating the vandalized data, writing custom SQL queries to fetch it, then restoring the data to my live site's database should not be necessary to restore some accidentally (or maliciously) deleted data. It's extremely time-consuming, clumsy, and sufficiently challenging that many forum owners would not even be able to do it.
It's even worse if you're trying to restore attachments, gallery images, or anything else that involves a physical file in addition to a database entry - then you have a database backup and
a filesystem backup to fish data out of. All of this trouble
can be resolved by extending the "Hide" feature to absolutely everything
, and making super moderators honour all the "Can permanently delete content?" usergroup permissions. I think that's what we're all asking for here.