Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    CROSSFIRE    |    Politics and Current Events    |    334 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 110 of 334    |
|    Bob Ackley to BOB KLAHN    |
|    Echo Rules    |
|    11 Jan 11 06:25:32    |
      Replying to a message of BOB KLAHN to BOB ACKLEY:               BK>>>>> No moderator name entered. No moderator identified.               RW>>>>> Perhaps if you had a Fidonet nodelist and were able to read it,        RW>>>>> you could then identify the moderator.               TR>>>> Klahn just made an attempt to hijack another echo and got        TR>>>> caught at it. He's now licking his wounds in other echoes.               BK>>> Richardson is lying.               BA>> He's telling the absolute truth, Klahn. Everybody that        BA>> witnessed your hijinks is aware of what you tried to do.               BK> And they are aware that you are lying here. Your ignorance may        BK> be correctable, but your choice to remain ignorant makes it a        BK> lie.               BA>> Not to mention that Earl saved the netmails he got when        BA>> Thom's system notified him that somebody was trying to        BA>> register HIS echo is someone else's name (yours). You               BK> Which does not change a thing, as you would know if you were not so        BK> ignorant of how Fido works.               BA>> tried the same trick some time back with POL_INC, and Earl        BA>> has that netmail too. Had either echo *really* expired as        BA>> you claim, Thom's system would not have rejected your        BA>> attempt(s) to claim them.               BK> And that is your ignorance. Thom's system works automatically,        BK> the elist robot. The echo does not have to be in the last issued         BK> Elist to be listed, but the next one. I told you before, look in the        BK> elists of the time. He was not listed as moderator. He was listed in        BK> the *NEXT* elist, not the last one. And you can't see the next elist        BK> until it's published.              Since that *NEXT* elist hadn't been published, how did you know the listing       had expired?               BK> I checked the elist before attempting to list an echo. You        BK> should check it before spouting off on what you don't know.              Let's take a big leap and assume for a moment that what you've posted here is       really       true and not one of your delusions. Why then, did Thom's elist robot (a)       reject your       attempt to list the echo and (b) warn Earl that you were trying to steal it?        The only       answer I can think of is that the listing had *NOT* expired as you continue to       claim.              When the elist entry for this echo did in fact expire, Earl was able to list       it in his       name with no problem, and Alan Hess later thanked him for picking it up.              Just in case you missed this post to me:              -----------------------------------------------       BK> I checked the elist before attempting to list an echo.              "Warning: bob.klahn@fidotel.com, bob.klahn@sev.org, (1:261/1500.0)       attempted to modify the record for area "ALL-POLITICS", but provided the       wrong password."              That was sent November 12, 2010. There was no list put out in October, but       the September list has this entry:              "ALL-POLITICS         All Politics Conference         Placeholder         Status: Active         Origin: Group: Fido         Distribution: BACKBONE         Gateways:         Language:         # Nodes: N/A Volume: N/A Rules:         Flags: |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca