In order to eliminate any action, it is clear that they need to be stored in order to be able to roll back to the old version or re-establish the remote. And since we're talking about web development, we usually have two choices: client and server. But to make sure that this information is stored on a client in a bucket or right on a page or a hz where, as I say, it's just like you said "great" (not "self"). So we have to keep it on the server, and since we're choosing a server, why don't we just skim the same OBD that's where it's all stored. That's why I think it's best to use the Flag Flag Scheme. Judging by the question, you're in the class of how to implement it, and that's not complicated. The only thing I want to add is the version, which, as an example, has been implemented in the editing of issues in this forum. In this way, it is possible for the OBD not only to mark a record of any kind as remote, but to implement a certain structure for the storage of post versions, comments, etc. With this structure in the OBD system, it is possible to cancel not only one action, but to return to any previous one, but it is already largely dependent on the task of whether it is necessary for you or is sufficient to simply cancel the removal.In addition, if a social network is considered, when the probe is removed, as far as I know, the scheme is again used, and it would be weird if the yuser is removed, the information left to it is missing from the entire portal, although sometimes it is required by the TK and then the cascades in the OBD or MPA will clean up all the data related to the art.