BF> Nah, the chair is appointed by the committee, so first you have to BF> be elected to the committee.
The FTSC Administrator is *NOT* required to come from the ranks of the FTSC. The charter specifically allows a non-member to assume the administrator position, provided he is selected by the standing members of the FTSC.
RS>> I would like to see more innovation in FTNs, but the battle RS>> against old standards/software/people just takes the fun out of RS>> it for me.
BF> Well, you've now seen my attempts. I'm sure that with you onboard BF> the FTSC could really start making a difference, cleaning out all the BF> dusty old stuff and paving way for some novelties.
FTS-1 really could be split into several documents. The stored message definition section is useful information, but not absolutely required for a FTS-1 compatible implementation. The packet header and packed message definitions are the key components to how things work in FidoNet. The FTS-1 session protocol is largely obsolete, although in theory any dialup node is required to support inbound FTS-1 sessions during their Zone's Mail Hour.
I can't remember the last time I saw a dialup FTS-1 session, incoming or outgoing. FTS-6 and EMSI sessions have largely taken over the dialup arena. There are even nodes supporting these protocols over Telnet or VModem connections (ITN and/or IVM flags.)
FTS-1 was originally designed back when 300 bps modems were state of the art.
