| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Nodes or member of the FIDONET |
Hello Vladimir. 18 Oct 04 12:36, you wrote to Ulrich Schroeter: US>> So there are comparable connection options available and in use, but US>> not reflected by the policy or fts-0001 document. So sysops using these US>> new options aren't no longer fidonet members? i think they are. VD> FTS-0001 is real expired, no one of standart are acting for same years! VD> Last standarts are acting for 2 years, but fts-0001 (.16) from 1995! So - VD> FTS-0001 can not criteria for FIDONET members. Myself and others have been trying for quite some time to get the FTSC to do it's job and change FTS-0001 to reflect the reality of the network today. They refuse to do so, and use some invalid excuse of a copyright that bears no legal weight as an excuse not to do so. US>> This and the layer incompatibility of part of todays fidonet US>> connectivity aren't reflected by policy nor fts-0001. So these parts US>> needs extensions to the fts-0001. The technical solution to bring US>> different layers together is a gateway like a zone gateway. There is a US>> leak between common practice and fts-0001 definition and this leaves US>> room for any quarreling ... VD> Yes. But revision must to be not only FTS, but all Policy. That's been tried too, and quite recently. Your current zone has the ability to single-handedly change policy, yet refuses to do so. --- GoldED/W32 3.0.1* Origin: MikE'S MaDHousE: WelComE To ThE AsYluM! (1:134/11) SEEN-BY: 633/267 270 5030/786 @PATH: 134/11 10 3613/1275 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.