• Re: Nodelist Development

    From Avon@21:1/101 to All on Sat May 30 14:34:22 2020
    On 29 May 2020 at 10:11a, alterego pondered and said...

    I dont think we should be "stuck" with how it was designed in the 90's.
    I do think we must make sure we dont break anything if we make changes - so consideration must be there.

    I've talked about using the ITN flag to show the telnet port. I still think that that is possible. (So it with the INA field could represent
    how a person connects to a BBS.) There are also other existing flags
    that could hold other data "U" for example. Or we can create our own. "WEB:....", "EML: ...", "SSH:...", etc which I dont think will break existing system, but I'm willing to try if somebody else is.

    The only limit that I'm aware of, is that a flag can only be 32 chars in length, so may be limiting for some web urls or email addresses...

    Hi all.

    Can we move this thread over to FSX_NET to discuss further and let's see if we can:

    - confirm a list of things we're trying to address / enhance etc.
    - develop some new standardised flags for the fsxNet nodelist
    - test this all out

    I have been trying to keep up with the threads here and in Mystic echo but would welcome the chance to consolidate thinking and some next steps over in the Network Ops echo.

    Thanks!

    Paul

    --- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From stizzed@21:4/156 to Avon on Sat May 30 01:06:25 2020
    Can we move this thread over to FSX_NET to discuss further and let's see if we can:

    - confirm a list of things we're trying to address / enhance etc.
    - develop some new standardised flags for the fsxNet nodelist
    - test this all out

    I have been trying to keep up with the threads here and in Mystic echo
    but would welcome the chance to consolidate thinking and some next steps over in the Network Ops echo.

    I think that is a terrific idea. I have been working on BLAM and node2bbi
    and have it importing and calling non-standard ports. We have much to
    discuss but as I have posted in the past, this is infinitely doable and its
    tie has come!

    I just turned on FXS_NET so Im just waiting for a message to show up and ill
    be there.

    Thanks Avon!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (21:4/156)
  • From Avon@21:1/101 to stizzed on Sat May 30 18:54:03 2020
    On 29 May 2020 at 09:06p, stizzed pondered and said...

    I just turned on FXS_NET so Im just waiting for a message to show up and ill be there.

    Suggest you try for a rescan of the echo using a netmail to Areafix with
    your password in the subject line and in the body use

    %RESCAN D=999

    This should pull it all in for you :)

    --- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From stizzed@21:4/156 to Avon on Sat May 30 03:06:03 2020
    Suggest you try for a rescan of the echo using a netmail to Areafix with your password in the subject line and in the body use

    %RESCAN D=999

    Tried that and got nothing but Ill try again

    Thanks Avon!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (21:4/156)
  • From Avon@21:1/101 to stizzed on Sat May 30 19:22:00 2020
    On 29 May 2020 at 11:06p, stizzed pondered and said...

    Tried that and got nothing but Ill try again

    I'll post there now also to help create something for you. That rescan should have worked.

    --- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)