home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 15 
 mark lewis to Shawn Highfield 
 Anyone? 
 15 Aug 14 14:41:28 
 
 On Fri, 15 Aug 2014, Shawn Highfield wrote to mark lewis:

 ml> true... that and lack of sleep, as in the previous incident, 
 ml> leading to misunderstandings...

 SH>   Lack of sleep is a big one for me as well. 

i hear ya... in my case, it was due to migraines and i had been up for close
to 48 hours or more... in his case, it was work related and then working on
the software instead of sleeping (from what i understand)... either way, both
of us were tired and it just went the wrong way... i got ambushed by my friend
and forced to go to bed with a dose of meds that put me out for a while...
   
 ml> ohhhoho! the thought being that jamnntpd is an existing product so 
 ml> start there and graft jam into ezy... or graft ezy bases into 
 ml> jamnntpd

 SH>   Exactly.  Since it's already working if I knew C my thoughts 
 SH> were to cram ezybase in there and voila.

 :)

 ml> and call it something else? TBH, i've been thinking of writing a 
 ml> nntpd in pascal to make it easier to interface with the bbs 
 ml> areas... maybe even one that used the existing user bases for 
 ml> group and area access permissions... but alas...

 SH>   I've started more then once.  I have good intentions of 
 SH> finishing it but then work gets in the way and I take a few months 
 SH> off again.

i know how that goes...

 SH>   If you ever did do it I'd test it / help add ezybase into it. ;) 

what i'd maybe like to do is to update the existing ezybase objects to the new
format... i don't know what the changes were between the older one and the
newer stuff... here's what my PostIt util's docs say about ezy support...

"The EZY definition is the base directory from which the EZYCom Message Base
areas will reside. I'm not familiar with EZYCom and can only rely on
information received from EZYCom sysops and the library code I am using. It
appears that the EZY definition is to be the base directory from which all the
EZYCom areas are built from. EZYCom areas seem to be divided into groups of up
to one hundred areas with each group of one hundred being located in a
dedicated AREA???? directory, two files per area. You may define only one EZY
path."  

there is/was also a 1024 area limitation...

)\/(ark

 * Origin:  (1:3634/12)

<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca