Bitcoin Forum

Take notice of the title "A "Back Door" to Liberate Bitcoin"

https://i.postimg.cc/FKcDG4Cf/20200125-143032.jpg

I just wonder when I browse the altcoin discussion section there are two post which is exactly the same (topic and title). I know that if you already post a topic or certain response the forum will prompt you that you already posted it. But why this post still reflecting on this?Altcoin Discussion (https://bitcointalk.org/index.php?board=67.0)

---

First post
https://bitcointalk.org/index.php?topic=5220555.0

Second post
https://bitcointalk.org/index.php?topic=5220556.0

There is a gap of post of 25mins. I'm thinking the user have some sort of internet connection error and thought that his post wasn't posted yet. But the forum still accept it? Is this normal to have duplicate post or something needed a fix?

AFAIK, the forum doesn't have a preventive feature to disallow double postings. Maybe PM the OP to delete the other one or just report it to the mods and they'll handle the duplicate post.

For me this 2 topic still on the forum because :
1. No one report the topic and keep refusing
2. Moderators are offline / busy / forgot


Yeah I agree, internet connection error make him thought the post was not posted. So, he do post again after 25 minutes later.  I will say it bug if the forum displaying 2 same topic but the real / record posted 1 only.

I see, maybe theymos need to fix this and not to allow double posting IMO to avoid same post lurking in some section if this incident occur again.


I already reported to mods as dual post.

Just check his profile and the post still double so it's not recorded as 1 post only. So it's not a bug but really a dual topic posted.

The good thing is he hasn't posted it on multiple boards because that means violating the unofficial forum rules but examining it I guess that is just an error on his part not that it's a forum fault.


I think there is no notification you'll be getting if you double your topic, I think it is just when you post a reply and you'll be notified that you already responded to it to prevent double posting I usually encounter that one when I get a slow internet connection but can't remember that notification to be honest.

I've reported the duplicated thread. Lets see how's the outcome.

And this is exactly the right approach.
Even moderators cannot have everything in view and need help.

Report thread, specify reference, wait a short while. Problem solved :)

The problem has rightfully been solved, the second post has been trashed by a moderator I think, quick response and thumbs up to all those who reported the post and who report posts when it's needed.

This thread can be locked imo now.

This doesn't happen often enough to justify making a change within the code, especially because the additional resources it would use to check whether someone has previously posted the same message would greatly outweigh the benefits of preventing users from posting duplicate content. Duplicate content is usually made on purpose where users look to spread their product or whatever to as many users of the forum as possible. Of course, as stated above the correct way of going about this is reporting the thread, and linking back to another thread of the duplicated content.

Sometimes this sort of duplicate content does go unnoticed, and it results in two different conversations at which the best thing to do would be to merge the threads together. However, I think that entirely depends on the quality of discussion.  Usually what happens is either the most active thread is kept or the one that was posted first. However, sometimes a thread that has been posted after the oldest one has better quality discussion, and is more active therefore sometimes its more appropriate to remove the older thread in that case.

I can see that second post has been trashed already. Thanks for our moderator. Thanks Welsh for clarification it seems this kind of incident is rare but good that we've seen this kind of bug. Gotta admit this would take time to implement if theymos will code for this sort of problem. Maybe in the future if the process is necessary already. I will locked the thread now.