Subj : linked
To   : Jasen Betts
From : Gordon Lewicky
Date : Wed Dec 18 2002 06:16 pm

 Quoting Jasen Betts to Gordon Lewicky 
 Subj. linked, dated 17-Dec-2002 16:25 

Hi Jasen,

 JB> They can go in the flags.. INA and IEM (or attached to the mailer
 JB> flags) the 157 limit  though may meed that there is less room got other
 JB> fields like sysop name, location, and system namee.

Yup, I know, and I think that is a sensable place to put them.
Plus it already works, and see no reason why we must hold to the
absolute definition of a flag, by not attaching an addy to it.

The only problem it can lead to is line length limitaions or field
length limitations and in most cases, this is a simple fix in the
code.

A hell of a lot easier then adding new fields, or moving addys
from the bbs name field to the location field.

As I've said, the real key is how do we differentiate between pots
and ion without having to force the use of PVT.

PVT should mean a non-directly contactable node, routable only,
until such time as one gets direct contact info from the node
holder. And that is all PVT should mean.

If we're to fix the nodelist, that is where we should start.

Cheers...
Gordon Lewicky (Pdk)

Sysop - Milky Way 1:153/307 NC 153
AdventureNet 33:500/150
email glewicky@telus.net

--- EzyBlueWave/2 V2.00 00F90260
 * Origin: Milky Way, Langley, BC [604] 532-4367 (1:153/307)

.