|P is for Practical|
Avoiding accidential repostsby LanX (Chancellor)
|on Feb 25, 2014 at 22:24 UTC||Need Help??|
This is not a feature request!
... more a meditation. :)
If we'd supply a unique id for each comment session, could this be used to reject or warn about accidental reposts?
I.e. after clicking "comment" a hidden field would contain something composed from parent-node-id + user-id + timestamp + random number and passed thru the "preview" and "create" stages.
After first posting this ID could be "disabled". Either by storing in the DB-table holding the final post or by caching it for x hours.
A considerable part of NTCs deals with such accidental duplicates and even experienced monks regularly fall into the trap (especially when using mobile clients)
Am I missing something?
If this was already discussed before please point me to the discussion.
( addicted to the Perl Programming Language)