Suggestion on accidental duplicate posts

The system has a catch to prevent accidental duplicate posts from going through.

Would it be possible to have a note left that a duplicate post has been made like whenever someone as posted a reply while we where typing, in red.

The system usually catches full duplicates and refers you to the plant in question. What it does not catch is variations in cultivar name. A cultivar named Gold Mine may be also vended as Goldmine. The system does not recognise that as a duplicate.

Whenever we make a dulicate in the games threads it doesn't do anything. Then you don't even know if a post went through or not. Until you look at it see what you thought you posted wasn't posted at all. If it came back and said you had made a accidental duplicate post then you could go back and repost.

I think Linda's referring to forum posts, and the system is set up a little differently to try to catch those. I think the only time a true duplicate post occurs is when someone has a quick "trigger finger" on their mouse or enter key, and the same post slides through twice (or more) in rapid succession.

In those cases, the system doesn't have a chance to detect the first post before the second one comes in on its heels, which is why the second one is allowed in.

As long as the first post arrives in adequate time for the system to register it, you can't post the same exact post within the same thread - the system will stop you.

Could it leave us a note saying a duplicate post has been posted? You know like it does when two people are posting at the same time, it comes back in red saying while you were typing another post was made. (Something like that)

That is something I don't know..it would be up to Dave to figure out if it could be added.

I think the system would have to realize what happened in order for it to pop up a message like it does now when someone else made a post while you were typing. And since the system doesn't recognize that you made two posts quick enough to stop the second one from going through, I'm guessing it wouldn't recognize it in time to put a notification on that screen either.

If it doesn't recognize it in time to display a message then why doesn't it go ahead and post it.

I am completely dumb when it comes to all this new technical stuff, but I am just asking.

Now you've confused me, I thought I understood your original question, but I have no idea what you're asking now! So I'll just try to explain my last post again. Basically, in order to pop up a message saying "you just made a duplicate post", the system would need to realize that you submitted two of the same post. But if the system had time to realize that the second post was the same as the first, Dave already has programming in place that would stop the duplicate post from going through in the first place. So you'd never wind up with a situation where a duplicate post got made and the system was aware of it, the ones that do get through are ones that are submitted very quickly after each other, so the system never even realizes it.

Let's say for example that it takes 10 seconds for the system to realize that a post has been made (I'm just making this up for the sake of an example--it probably takes much less time than that). You click "send" to submit a post, then 2 seconds later while you're still on that same screen, you accidentally click send again. The system doesn't catch your duplicate because it's only been 2 seconds rather than 10, so it doesn't know the first post went through yet. Then 2 seconds after you hit send the second time, you're taken to that next screen (the one where you can choose to watch/unwatch, return to the thread, etc). This is the screen where you're wanting a message to pop up saying you made a duplicate post, but since 10 seconds hasn't gone by yet, the system doesn't realize you posted twice yet. So there's no way it could put a message there telling you there's a duplicate.

Then in a second example, let's say you click send, then you wait 20 seconds and submit the same post (don't know why you'd do this, but this is just an example!). Now since more than 10 seconds has gone by, the system knows your first post was there, and it'll see that you already made that post, and it won't let the second one go through.

My times are obviously made up, but I hope it makes it clearer that if enough time has gone by between posts for the system to know there was a duplicate and alert you, it wouldn't have let the duplicate through in the first place. Only time the duplicates sneak through is when things happen too quickly and the system doesn't realize yet that a particular post already got through. And if the system doesn't know a duplicate sneaked through, there's no way for it to tell you about it.

You are talking about hitting the send button twice to get a duplicate post. I'm talking about maybe I made a post yesterday with the word "maybe" then I come back two days later and type the same word "maybe'. Then is won't post that second post because it is a duplicate post.

Yes, that's correct. If you make a post that's identical to a post you already made in that same thread, then it won't let the second one through. Sorry, that's not at all what I thought your question was. So I guess I'm not sure what you were originally asking for then?

I think what Linda is asking for is, instead of getting a non-response from the system, it would be preferable to receive an error message of some kind.

In the instances where the system has detected a duplicate, instead of just not letting you post it (and assuming you'll figure out why it won't post), it would return an error message stating something like:

Thank you Terry you are very correct.

ecrane3 I am so sorry I wasn't very clear with my question. But I do want to thank you so much for trying to help me.