Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 7695  |
|  Maurice Kinal to Carol Shenkenberger  |
|  the fix is in  |
|  27 Dec 20 23:32:10  |
 
REPLY: 7575.asian_li@1:275/100 244cdf1d
MSGID: 1:153/7001 5fe9197a
-={ Corrected DateTime for those in the know: 2020-12-27 15:32:10 -0800 }=-
Hey Carol!
CS> Anyone can make a proposal. It just doesn't get changed to a
CS> 'standard' unless widely in use.
It occurs to me that 'widely in use' for something that isn't a 'standard' is
going to be difficult to prove. However I am formulating an evil, demented
plan that would scan msg's posted in FTSC_PUBLIC that contain the so-called
corrected DateTime stamp, known as '%F %T %z' in strftime-speak, no matter
where it is placed in the msg_body which includes kludges or such as in the
top line of this reply or even quoted. Thus this reply if posted in
FTSC_PULIC would be counted as both a post and a positive hit for the
corrected DateTime stamp whereas the msg I am replying to would only be
counted as a post and not as a hit for the corrected DateTime stamp.
I haven't written the routine yet but am thinking Jan. 1, 2021 would be the
target date for implimentation.
And yes I do realize that I am a prolific poster in FTSC_PUBLIC which could be
interpretted as skewing the data but to be honest I have no issue with that.
How about you?
Life is good,
Maurice
... Don't cry for me I have vi.
--- GNU bash, version 5.1.0(1)-release (x86_64-motorshed-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
SEEN-BY: 1/123 18/200 90/1 105/81 106/127 120/340 123/131 124/5016
SEEN-BY: 153/105 135 757 802 6809 7001 154/10 203/0 221/0 1 6 360
SEEN-BY: 226/30 227/114 229/101 424 426 452 664 1016 230/0 240/1120
SEEN-BY: 240/2100 5138 5411 5832 5853 249/206 317 400 261/38 280/464
SEEN-BY: 280/5003 288/100 292/8125 310/31 317/3 320/219 322/757 335/364
SEEN-BY: 342/17 200 396/45 423/81 120 460/58 633/280 770/1 2454/119
SEEN-BY: 4500/1
PATH: 153/7001 757 221/6 1 280/464 240/5832 229/426
|
[ << oldest | < older | list | newer > | newest >> ]