It will be less risk with an official feature than people trying to run custom commands.
GitHub has permanent repo delete. I’ve been fine. They make you input the name of the org and the repo before deleting, and your password, to verify you want to do it.
I don’t see why this has to be blocked. It’s just annoying.
Yes. 100%. I don’t want junk in my DB, especially not jibberish junk from bots trying to get posts approved and wasting my time. Why would I want to keep that stuff?
Please give us an official tested way of doing it. Or at least a timer option to delete deleted posts after XX number of days.
You could add triple verification in the UX flow to reduce risk. For example, similar to the “delete 124 users” message when bulk deleting users, but also prompt for re-authentication, or something, to make it even less risky. Perhaps put up a flashy red warning message that has to be accepted. You can eliminate the risk by making people think thrice when bulk deleting posts.
The worst possible solution for this type of thing is no solution at all, from my end user perspective. I absolutely get annoyed thinking about this, that I can’t do something that I feel should be easy to do in the UI (with triple or quintuple verification, that’s fine!).