| |
N1URO > PACKET 11.12.14 14:57l 45 Lines 2339 Bytes #999 (0) @ WW
BID : 54766_N1URO
Read: GUEST
Subj: Procedures and protocols
Path: IZ3LSV<IV3SCP<IW0QNL<VE2PKT
Sent: 141211/1350Z @:VE2PKT.#QBC.QC.CAN.NOAM #:61283 :54766_N1URO
R:141211/1334Z @:N1URO.#CCT.CT.USA.NOAM #:54766 [Unionville] $:54766_N1URO
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : PACKET@WW
Greetings fellow packeteers and sysops, and happy holidays. I would like to
point this bulletin out to sysops and programmers of various packet
softwares and plead with them to dig deeper into protocol specifications
before releasing things into the public. As a coder myself I try to do
just that. Not fully investigating things can cause a mess and even
separate networks leaving those who still use the mode confused and even
stranded.
For years, we've had standards that continue to work yet aren't being
followed. Documentation is available as is plenty of open source software
to look at code to get an idea on how things are done. Recently, I've seen
a bunch of WP bulletins being spread around the world in non-WP protocol
format. Going back into the previous millenium we had WP and it worked
well. PBBS White Pages should be sent as a Private not a Bulletin. Not
until somewhat recently are they coming through as Bulletins and making
a muck of the lists. RLI, MSYS, FBB back then never nor do they now ever
send WP updates via Bulletin. Why is this protocol of procedure not being
followed? If you run a PBBS that does this, you may want to halt your
distribution of WP Bulletins and request the author of the program fix
this issue.
The World Wide Convers system is a series of servers linked together which
host client connections via RF or using tcp port 3600 for user to multi-user
keyboard conversations. It appears this too is not being followed anymore. In
this day and age when almost every system is tcp/ip compatable, it should be
quite simple to maintain the protocol of the global convers system. Is there
a reason it's not? There's a handfull of softwares that do this, some may
not even be attended to and are closed source in nature - very bad for
this reason.
Imagine how broken the global DXCluster nodes would all of a sudden become
if the authors of the various cluster softwares didn't keep in line with
following protocol. Protocols are somewhat our own disciplines and when
we don't abide by them, we get out of control and things stop working which
gives others a valid reason not to use the mode anymore.
Just my two cents. Again happy holidays one and all!
73 de N1URO
Read previous mail | Read next mail
| |
