bkil vs. programming

Here is a link where you could theoretically monitor Google outages: https://www.google.com/appsstatus#hl=en&v=status I had a problem with Google services just recently. However, as I wanted to verify whether the problem is on my side, this monitoring site was down as well. At the same time, the third party reports on alternative sites started to grow: http://outage.report/google http://downdetector.com/status/google http://aussieoutages.com/status/google This highlights why we should not put all our eggs into the same basket.

https://en.wikipedia.org/wiki/Eyewitness_memory#Encoding https://en.wikipedia.org/wiki/Misinformation_effect#Basic_methods https://en.wikipedia.org/wiki/Memory_conformity#In_and_out_of_lab_settings https://en.wikipedia.org/wiki/Eyewitness_identification#Causes_of_eyewitness_error https://en.wikipedia.org/wiki/Eyewitness_testimony#Reliability https://en.wikipedia.org/wiki/Dashcam Lessons to learn from dashcams: live traffic accidents (not for the faint of heart) birds surfing vehicles (funny)

We need mail client software support for the following. Make it automatically prepend a few identifier characters and a (decimal) sequence number to the subject line of outbound messages. The sequence number would get incremented, and could perhaps wrap around. In case of replying to a similarly formatted message, the mailer could also send back the highest number up until all mail have been successfully received from the given sender. The MUA could automatically resend the lost messages. These measures would ensure reliability - just like how they do it in TCP! I know you could easily implement this in Emacs, but I would like to see this in some more mainstream mail user agents. Add 1: Of course we could also create a new header field for this purpose. Also note that this method could replace message disposition notification in almost all cases. RFC?