When creating a new post, can the yellow
Post
please be grayed out, to indicate it's being posted and prevent any further clicking.
At present time it's rather common for people to make half a dozen duplicates.
Life is like a camera: Just
focus
on what's important,
capture
the good times,
develop
from the negatives, and if things don't work out,
take another shot
!
Yeah, sometimes on Chrome, the tab doesn't show the page is loading after clicking submit, making some people (like myself) think they simply missed the post button.
°l||l°
Modest Skillers
T7 Citadel | Skilling clan recruiting players. °l||l°
•ï¡÷¡ï•
Cwar United
for CW games/Ardy task/Trim req. •ï¡÷¡ï•
120 Summoning Familiar ideas
.
03-Jan-2021 09:57:31
- Last edited on
03-Jan-2021 09:57:44
by
UrekMazino
The thing is, when the browser is loading after clicking the post button, you can purposely spam click the post button again to create multiple message posts or threads in same post time!
Tuffty
said
:
I make very few duplicates very few. So far None this year.
Lol impressive.
As to the duplicate threads forum lag does suck. However we all can tell the difference between lag and serial spam. It's easy to mop up if necessary. Although if they didn't replicate to begin with, would certainly be even easier...
When the day becomes the night and the sky becomes the sea, when the clock strikes heavy and there’s no time for tea; and in our darkest hour, before my final rhyme, she will come back home to Wonderland and turn back the hands of time.
I agree it's a nice fix. With some optimism.
Life is like a camera: Just
focus
on what's important,
capture
the good times,
develop
from the negatives, and if things don't work out,
take another shot
!
The first way is using a little Javascript/jQuery to disable the Post button when clicked so that it can not be clicked more. The drawback to that is when users who have disabled Javascripts in their browser settings post, the button will not disable.
The other way (or perhaps the two ways could be combined, who knows) would be to add a check on the server side that compares information being submitted (whether it be a new thread or post) and if the same exact information is received by the server from the same exact user more than once over a period of 'x' minutes, the server can just ignore every subsequent identical submission from that user. The draw back to that option is the extra processing the server would now be doing to compare data for that purpose could exacerbate a lag issue if that is what the user is experiencing.
•
Spearmint30
•
¤
Food scientists have finally managed to remove the mint flavor from gum! The ex-spearmint was a success!
Wait as long as until the browser issue solves itself ... or ... log-out and pick another moment of the day to do what you wanna do but refrain from hitting the postbutton multiple times because you get no instant response.