= Сообщение: 4092 из 7124 ====================================== FTSC_PUBLIC = От : mark lewis 1:3634/12.73 09 Dec 18 12:11:32 Кому : Michiel van der Vlist 09 Dec 18 12:11:32 Тема : Candidates vision request FGHI : area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0d4faa На : area://FTSC_PUBLIC?msgid=2:280/5555+5c0ac9e7 = Кодировка сообщения определена как: CP437 ================================== ============================================================================== On 2018 Dec 07 20:28:38, you wrote to Fred Riccio:
MvdV>>> Then obviously the combination of Jerry's script and binkd does MvdV>>> not qualify as a properly configured FTSC complient software.
MV> FTSC complient as documented by the FTSC in FTS-5001.
FR>> YOUR opinion DOES NOT define current practice. The software in use FR>> does.
MV> So you say, but that is just YOUR opinion.
no, it is the opinion of many others, too...
MV> Documenting current practise and calling it a standard is fine as long MV> as current practise is unambiguous and consistent.
that is not the fidonet way... fidonet is about experimenting...
"Very simple; it is a hobby, a non-commercial network of computer hobbiests ("hackers", in the older, original meaning) who want to play with, and find uses for, packet switch networking. It is not a commercial venture in any way; FidoNet is totally supported by it's users and sysops, and in many ways is similar to ham radio, in that other than a few "stiff" rules, each sysop runs their system in any way they please, for any reason they want." - FidoHist.Txt, 7/14/85, Tom Jennings, the founder of Fidonet
there has been a slow and exorable movement to try to narrow fidonet's capabilities and stifle experimentation and development of newer capabilities for moving traffic from one system to another...
MV> Unfortunately there is not one single current practice.
as it should be... they are all common/current practise...
MV> There are softwares around that do things in conflicting ways. MV> Documenting all of it as a standard is unworkable.
the FTSC doesn't document software... it is easy enough to put in a note "if you use such'n'such mailer, you need to do this intead" or similar...
MV> Making standards is making choices between incompatible alternatives.
that's why there are multiple standards... software chooses which standards they will follow... those they do not choose to follow do not apply to them no matter what others' think...
MV> Demanding that the FTSC documents all current parctises as standards MV> is asking for a mission impossible.
who is demanding such? the FTSC set the goal themselves when the group was first put together... that goal has remained the same ever since...
)\/(ark
Always Mount a Scratch Monkey Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong... ... Have a day - manic depressive. --- * Origin: (1:3634/12.73)
