On 5/15/19 2:01 PM, Aaryan Bhagat wrote: > Mark thanks for the clarification, > I understand the principle now for this behaviour. > It would be sort of nitpicking but is it good enough to open an issue so that > this behaviour should be avoidable?( I do not know the exact way to avoid it > yet). > > Alteast we can write a Disclaimer something like > "Do not click the Send button twice" ( In a more soft and pleasing way, not > like this exactly )
It would be appropriate to add a warning, particularly if response can be slow. You can open an issue for that. Maybe something like "Please do not press Send more than once. Doing so will create a duplicate post." Actually modifying HyperKitty to detect that such a post is a duplicate would I think be quite cumbersome. Hyperkitty would have to remember all the posts to check for a dup. It is not enough to check the archive because Hyperkitty sends the post to core and doesn't archive it until it returns which may not yet have happened at the time of the second Send. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
