The discussion addresses a bug where the duplicate post check includes deleted posts, preventing users from reposting similar content after deletion. Steradiant reports that after deleting a post in the wrong topic and trying to repost it in the correct one, a similarity error occurs. Moin clarifies whether the issue involves fully deleted posts or those marked as deleted by the author, noting that allowing restoration could undermine the anti-spam measure. They also mention that the default 5-minute unique post min delay is reasonable for spam prevention. Steradiant suggests restricting the check to users with low trust levels or applying the same check when restoring posts.
Steps to reproduce:
Expected behavior: The post is sent.
Actual behavior: An error message that the post is too similar to a message recently posted
Are you talking about deleted post that are removed from the data base, deleted posts that are only visible to users allowed to see deleted posts or a post deleted by a user that is still visible as “(Post deleted by author)”?
In the last case the user could still restore their post after posting it a second time. That would render this measure against double posts ineffective.
I have also expirienced that I accidentially posted in the wrong topic, deleted my post and had to wait a few minutes before I was allowed to post it again. By default unique post min is set to 5 minutes. I think that’s an acceptable waiting time to benefit from a spam-free forum.
I am talking about a post deleted by the author. Maybe restrict this precaution to users with low TL?
Alternatively, one could run restoring a post against the same check.