TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5fb38d76
REPLY: 1:153/7001.2989 5fb2eef0
Hi Maurice,

On 2020-11-16 13:28:16, you wrote to me:

 WvV>> That was the case untill last year, when the new chairman forgot
 WvV>> about it, and it was moved up a couple of months.

 MK> I recall that.  Seems an odd thing for the chairman to forget about.

He was new to the job. And the FTSC is probably not very active, since the
previous chairman left. But I don't really know, except I see no updated or
new documents apear, so I could be wrong...

 MK> We'll see when it comes up and in the meantime I'll think about it.
 MK> Thank you for your encouragment although I have to wonder if I am not
 MK> stepping into something that would be best to leave alone.  It might
 MK> turn out I have more impact - if indeed I have ever had any impact -
 MK> as an outsider to the FTSC.  From this perspective it doesn't appear
 MK> being an FTSC member has any real influence over so-called standards.

 MK> Am I missing something?

The FTSC is about documenting current practise. So if you think you can change
the standards to include general internet practise, your in the wrong place.
You're probably better of in for instance NET_DEV and try to convince other
developers to change their products to do so. But that can only be done in a
backwards compatible way, because of all the legacy software that is still in
use but can't be changed, because the developers left fidonet (a long time
ago).

And bitching about it in ASIAN_LINK has very little to no effect. ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 154/10
SEEN-BY: 203/0 221/0 226/30 227/114 229/101 424 426 452 664 1016 240/5832
SEEN-BY: 249/110 206 317 400 280/464 5003 288/100 292/8125 310/31
SEEN-BY: 317/3 322/757 342/200 396/45 423/120 633/280 770/1
PATH: 280/464 229/101 426