This is the scenario where I think I've seen this happen.
- You prepare your reply, click "create"; the servers running a bit slow so you switch to another tab for a few seconds or minutes.
- When you return, you notice a /msg (that was probably there from before), and either click to browser the reply node, or send /msg response.
You fail to notice that the create hasn't completed.
- You back up to get back to whatever you were doing before you switched away, see the create button and click again. Dup.
Is that a realistic scenario? I'm not sure. You rarely think to take detailed notes before the duplicate happens.
But if it is, the absence of nodelets might prevent it. Not a big argument in favour of it, but may a little icing if it comes about.
Which it has for me--via css--I am gleefully typing this reply in a (zoomed 140%) full-screen wide textarea. If I could avoid generating the load of the nodelets, I would willingly.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Rather complicated for it to account for "a lot" of dups.
And such simplistic re-submit is caught by simplistic protections. It isn't hard to thwart the simplistic detection due to races. But your scenario introduces extra time which makes it less likely to be able to produce an actual dup.
Update: I even re-submitted this reply just to verify that the simplistic detection was working. I indeed got sent to Duplicate Post Warning.
You can further complicate your scenario by adding extra "edit" (and possibly "preview") step(s) after going "Back" and before hitting "Create" again and then it results in near-duplicate nodes. But it also makes it even less likely to account for "a lot" of them.
| [reply] |
| [reply] |
It will be interesting to see if there is any change in the frequency of duplicate posts made by those that have made the changes to their CSS. UPDATE This duplicate was done as an experiment, it was posted without clicking the create button, it seems to happen to me when I have multiple nodes open and I am writing or previewing a post, moving to another tab and perhaps voting on that node by pressing the Enter key rather than clicking preview / post somehow also changes the focus on the Preview / Create page and the duplicate is created (I think).
| [reply] |
| [reply] |
Reminds me of my need to be able to remove duplicate posts in which there is only a small difference.
I've seen multiple times that accepting a post after review took soooooo long that I got a timeout.
After doing <back> and [create] again - maybe after adding a line to explain something that sprung up to add during the submission wait, both posts have been accepted even thought the first clearly gave the feedback of a timeout.
In this case I would love to be able to remove the first post.
Enjoy, Have FUN! H.Merijn
| [reply]
[d/l] |