Text 607, 91 rader
Skriven 2007-07-29 12:47:27 av Roy Witt (1:397/22)
    Kommentar till text 597 av Jeff Smith (1:14/5)
Ärende: The Rulz
================
28 Jul 07 20:17, Jeff Smith wrote to Thom LaCosta:

 RW>>> That doesn't work that way in HAM. It only works that way in
 RW>>> LaCosta's twisted mind.

 TL>> You personal attcks, which you often use, don't do you any credit.

 JS>      Without taking sides let me ask a question or two. Did you
 JS> contact Roy informing him that the listing for the echo had expired
 JS> and inquire about elisting the echo tag yourself IF he had no further
 JS> interest?

No. I know that he's been collecting amateur radio related echoes since
Fidonet has begun to die out. Thus, I knew this would come to a head one
of these days. Especially after I deliberately allowed the listing to
expire, since the Elist is no longer a viable resource. i.e. Too many
false listings with LaCosta alone having 67 echoes listed under his name.

I think Bobby Queen, the echo listing collector may have held more, but I
may be mistaken. In any case, it's a recognizable flaw in some Fidonet
sysops that seems to have invaded LaCosta's brain.

 JS> This is seperate from any automated notifications that your
 JS> system might have sent to Roy.

i.e. I knew it was going to expire 180 days after I listed it for the last
time. On the 210th day, supposedly it would have dropped from the list,
had LaCosta not relisted it before that time. i.e. There was another 30
day grace period that the echo could be relisted by me or the echolist
keeper. He didn't let it go to the end of grace period before he relisted
it.

 JS> I know that you two may dislike each other.

Heh. That's a given. At one time, I defended the elist, but he failed to
live up to his own standards, so I stopped. Oh, and he'll tell you that I
played with the elist robot, just to screw with it. Which is incorrect.
Had he lived up to his published standards, no one would have to 'screw
with it'...

 JS> I know that Roy may have forgotten to renew the echo listing.

I didn't forget, as I've stated above.

 JS> It just seems that the echo will end up on the losing end because you
 JS> two feel you must engage in and prolong this pissing contest.

All he has to do is 'go away'...I won't go away until he conceeds that
his claim to the HAM echo is a bad move on his part. With 67 echoes to
watch over, he'll have a hard time getting rid of me.

 JS> Is your elisting of the echo tag based on your interest in the
 JS> AMATEUR_RADIO echo or are you more interested in sticking it too Roy?

No, his interest is in the HAM echo; one more for his 'ham radio' echo
collection.

 JS>      Lets hope you both decide on what is best for the echo and not
 JS> use the echo as a pawn to get back at each other. There is enough BS
 JS> with echos as it is.

I've been the moderator of HAM since it was abandoned by Jeff Edmonson and
his girl friend gave me the password to the echolisting, c1997-98. (they
split up and he left Fidonet)

The rules of the HAM echo have been posted on a regular basis since then.
Accept for days when I haven't had a feed to the echo for reasons beyond
my control.

Michiel van der Vlist tried to 'taker over' the echo when the part of
California I lived in was on fire. I couldn't contact my RC (as a RIN), so
my nodelisting was dropped. It took nearly a month to get back online and
MvdV, as you can tell, is not the moderator there and his feed is set to
'read only' after continuing a program of harrassment.

I accomplished that by proving to MvdVs feed that in spite of the error in
the echolisting showing LaCosta as the moderator.

Since LaCosta's feed doesn't hold the echolisting in high esteem either,
not being as believable as it once was, I don't think it would be a
problem getting him to set LaCosta's accesss to read only as well.


                R\%/itt


"Beware the lollipop of mediocrity! Lick it once and you'll suck
forever..."

--- Twit(t) Filter v2.1 (C) 2000
 * Origin: SATX Alamo Area Net * South * Texas, USA * (1:397/22)