| |
KB2VXA > PACKET 20.04.12 13:21l 33 Lines 1375 Bytes #999 (0) @ WW
BID : 17116_VK6ZRT
Read: GUEST
Subj: Re: VE3WBZ > VXA comments
Path: IZ3LSV<IK2XDE<DB0RES<ON0AR<VK6HGR<VK6ZRT
Sent: 120420/1207Z @:VK6ZRT.#BUN.#WA.AUS.OC #:17116 [Boyanup] $:17116_VK6ZRT
From: KB2VXA@VK6ZRT.#BUN.#WA.AUS.OC
To : PACKET@WW
Hi Pete and all,
First things first, as I wrote in my last post in so many words now that
I have explained FULLY and expect Bob to understand regardless of the
outcome (I expect no change) it ends here. No sense whipping a dead
horse, I've said my piece.
Second, I'm just a bit puzzled but not entirely having read a few recent
posts concerning piurated callsigns. A JA at a VK BBS isn't so unusual in
itself, hey, look at me. Then comes the e-mail AD with a G4 user name?
Somehow they just don't go together but either one can be faked easily
enough. Echolink and various remote internet control stations require
callsign validation but it's not so easy as using the FCC database as in
other countries their DBs are not open to public access and registering
on a callsign lookup site is optional. So what's a sysop to do? Like the
king said, a puzzlement.
That kind of wanders into a different subject but still is of concern,
what should be of no concern is the "BBS SPAM" that's easily ignored. I
put that in quotes being it all comes down to POV and a notable hamfest
phrase; one man's junk is another man
's treasure. Oops, the return key got in the way. (;->)
73 de Warren
Station powered by JCP&L atomic energy, operator powered by natural gas.
Message timed by NIST: 12:01 on 2012-Apr-20 GMT
Read previous mail | Read next mail
| |
