Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Communications Echo  <--  <--- Return to Home Page
   Networked Database  Communications Echo   [13 / 36] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    Andrew Leary   Abandon?   April 8, 2017
 12:59 AM *  

 On 2017 Apr 07 23:19:18, you wrote to me:

 ml>>>> i haven't seen the FAQ posted in a long time... you can close it if
 ml>>>> you like but i would keep the echolisting in place if it were me...

 DH>>> I've never had a copy of the FAQ, so that would explain why I
 DH>>> haven't posted it! :-) Do you want the job?

 ml>> oh wow! i wonder who it was that took over the echo some years back
 ml>> that i gave a copy of that FAQ to? that was, i'm guessing, roughly 20
 ml>> years ago... i don't even know if i still have a copy here any
 ml>> more... i'll have to dig around on the main system and see if it is
 ml>> still hiding out there...

 AL> Gord Hannah, IIRC.

i definitely remember gord's name... what i remember about that situation was
that someone had the echo and was posting the FAQ... they disappeared and
someone else took over but they didn't have the FAQ... i sent it to them... now
 we have what is a similar situation... i just don't recall if it was gord that
 i sent the FAQ to or not...

 ml>> as for "the job", which one? the one of moderator or the one of
 ml>> posting the FAQ (if the FAQ still exists somewhere)?

 AL> I might have to check out some old backups to see if I still have a
 AL> copy somewhere.

if the echo is archived over on ozzmosis, they may have a copy, too...

[time passes]

YUP! it was gord that got the echo relisted in the echolist back in 2002/2003
and took over the moderatorship... he posted the 12 post primer from then until
 Mar 2011... richard webb took over the echo in Jun 2011... in his rules, he
posted this link to the COMM primer which is the FAQ, IIUC...

  http://www.filegate.net/epub/ep-ascii/comprim...

it looks like dallas took over moderatorship Sep 2014 and started posting the
rules with MSGPOST... this was after richard left fidonet and handed all of his
 echos over to others... dallas and i were benefecieries as was another couple
of folks...

here's two links to the COMM archive on ozzmosis...

newest posts
  https://fidonet.ozzmosis.com/echomail.php/com...

the initial posts
  https://fidonet.ozzmosis.com/echomail.php/com...

the second link will change as more posts are archived...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Vermont USA: 9 months of winter, 3 months of darn poor skiiing
---
 * Origin:  (1:3634/12.73)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Communications Echo  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0806 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_8qqsfnbdnj4m86ia1fiurqj8g7, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_8qqsfnbdnj4m86ia1fiurqj8g7, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_8qqsfnbdnj4m86ia1fiurqj8g7, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0