1. Forum
  2. FidoNet
  3. POINTS

  • oxp: how does it distinguish FREQ systems?

    From August Abolins@2:221/1.58 to Martin Foster on Sun Jan 19 18:25:00 2020
    Hello Martin!

    When I proceed with a FREQ, oxp will sometimes pop up a warning:

    +-----------------------------------------------------------------+
    | Nodelist says: No requests at this BBS. Try requesting, anyway? |
    | |
    | > Yes < No | +-----------------------------------------------------------------+

    But, I know that the system DOES allow file requests, for example:


    +------------------------------------------------------------------------+
    | <<PRISM BBS, Slaterville Springs NY 1:261/38 -Unpublished- |
    | <<PRISM BBS, Slaterville Springs NY 1:261/100 -Unpublished- | |------------------------------------------------------------------------|
    | Status Node Node list NODELIST.017 |
    | Sysop Janis Kracht |
    | Flags CM,INA:filegate.net,IFT,ITN,IBN | +------------------------------------------------------------------------+

    and, "Flags CM,INA:filegate.net,IBN:24555,IFT,ITN" for the 2nd entry
    above.


    What is OXP looking at in the nodelist to tell me "No requests at this BBS"?



    ../|ug

    --- OpenXP 5.0.42
    * Origin: /|ug's EuroPoint (2:221/1.58)
  • From August Abolins@2:221/1.58 to Martin Foster on Sun Jan 19 19:21:00 2020
    Hello Martin!

    ** 19.01.20 - 18:20, August Abolins wrote to Martin Foster:

    +----------------------------------------------------------------+
    | <<PRISM BBS, Slaterville Springs NY 1:261/38 -Unpublished- |
    | Flags CM,INA:filegate.net,IFT,ITN,IBN |
    +----------------------------------------------------------------+

    What is OXP looking at in the nodelist to tell me "No requests at this
    BBS"?


    NEVERMIND... I think I found my answer in the EPILOG section D of the nodelist.



    ../|ug

    --- OpenXP 5.0.42
    * Origin: /|ug's EuroPoint (2:221/1.58)
  • From Mark Lewis@1:3634/12 to August Abolins on Mon Jan 20 07:54:14 2020
    Re: oxp: how does it distinguish FREQ systems?
    By: August Abolins to Martin Foster on Sun Jan 19 2020 18:20:00


    When I proceed with a FREQ, oxp will sometimes pop up a warning:

    [...]

    But, I know that the system DOES allow file requests, for example:

    the following is taken from the end of the fidonet nodelist... it is actually copied from FTS-5001 which can be found here

    http://ftsc.org/docs/fts-5001.006

    ;S D: FILE/UPDATE REQUEST FLAGS:
    ;S
    ;S The following flags indicate the types of file/update requests
    ;S supported.
    ;S
    ;S
    ;S |--------------------------------------------------|
    ;S | | Bark | WaZOO |
    ;S | |---------------------|---------------------|
    ;S | | File | Update | File | Update |
    ;S | Flag | Requests | Requests | Requests | Requests |
    ;S |------|----------|----------|----------|----------|
    ;S | XA | Yes | Yes | Yes | Yes |
    ;S | XB | Yes | Yes | Yes | No |
    ;S | XC | Yes | No | Yes | Yes |
    ;S | XP | Yes | Yes | No | No |
    ;S | XR | Yes | No | Yes | No |
    ;S | XW | No | No | Yes | No |
    ;S | XX | No | No | Yes | Yes |
    ;S |--------------------------------------------------|
    ;S
    ;S
    ;S
    ;S The following software is qualified to
    ;S use the appropriate file request flag
    ;S according to information provided by
    ;S developers:
    ;S
    ;S |-----------------------------------|
    ;S | Flag Software Package |
    ;S |-----------------------------------|
    ;S | XA Frontdoor 1.99b and lower |
    ;S | Frontdoor 2.01 and higher |
    ;S | Dutchie 2.90c |
    ;S | Binkleyterm 2.1 and higher |
    ;S | D'Bridge 1.2 and lower |
    ;S | Melmail |
    ;S | TIMS |
    ;S | Xenia |
    ;S |-----------------------------------|
    ;S | XB Binkleyterm 2.0 |
    ;S | Dutchie 2.90b |
    ;S |-----------------------------------|
    ;S | XC Opus 1.1 |
    ;S |-----------------------------------|
    ;S | XP Seadog |
    ;S |-----------------------------------|
    ;S | XR Opus 1.03 |
    ;S | Platinum Xpress |
    ;S |-----------------------------------|
    ;S | XW Fido 12N and higher |
    ;S | Tabby |
    ;S | TrapDoor No update processor|
    ;S | The Brake! |
    ;S |-----------------------------------|
    ;S | XX Argus 2.00 and higher |
    ;S | BeeMail
    ;S | D'Bridge 1.30 and higher |
    ;S | Frontdoor 1.99c/2.00 |
    ;S | InterMail 2.01 |
    ;S | McMail 1.00 |
    ;S | T-Mail |
    ;S | TrapDoor - Update Processor |
    ;S |-----------------------------------|
    ;S | None QMM |
    ;S |-----------------------------------|



    )\/(ark
    --- SBBSecho 3.10-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From August Abolins@2:221/360 to Mark Lewis on Mon Jan 20 17:32:24 2020
    On 20/01/2020 7:49 a.m., mark lewis : August Abolins wrote:

    the following is taken from the end of the fidonet nodelist...
    it is actually copied from FTS-5001 which can be found here

    http://ftsc.org/docs/fts-5001.006

    ;S D: FILE/UPDATE REQUEST FLAGS:;S;S The following flags
    indicate the types of file/update requests;S supported.;S;S
    ;S |--------------------------------------------------|
    ;S | | Bark | WaZOO |


    Hello mark!

    Yes.. Very nice. Thank you.

    I found the same info myself a few minutes after my initial post.

    Suggestion.. The nodelist should have the "FTS-5001.006" source
    reference specifically mentioned, and a reference to the website.

    That would help demystify the Fidonet-of-Things(tm). ;)

    Over time, I have found that the extra comments in the nodelist very educational. It almost looks like a user-manual.

    Back on topic.. so there are only six "Xx" flags?

    Do you have any insight on why there is a gap from XC to XR, and why not
    just carry on with XD, XE, XF, XG, etc?

    BTW.. Sometimes, I find there are discrepancies in what the nodelist
    says, and what the system on the other end reports. :(

    --- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Martin Foster@2:310/31.3 to August Abolins on Sat Feb 1 09:14:00 2020
    Hello August!

    * 19.01.20 at 18:20, August Abolins wrote to Martin Foster:

    When I proceed with a FREQ, oxp will sometimes pop up a warning:

    +-----------------------------------------------------------------+
    | Nodelist says: No requests at this BBS. Try requesting, anyway? |
    | |
    | >> Yes < No |
    +-----------------------------------------------------------------+

    Yes it does and I've always regarded that as a nice feature :)

    But, I know that the system DOES allow file requests,

    Some SysOps don't always keep their nodelist file request flags up to
    date.

    Regards,
    Martin

    --- OpenXP 5.0.43
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From Martin Foster@2:310/31.3 to August Abolins on Sat Feb 1 09:16:00 2020
    Hello August!

    * 20.01.20 at 17:34, August Abolins wrote to mark lewis:

    [snip]
    BTW.. Sometimes, I find there are discrepancies in what the nodelist says, and what the system on the other end reports. :(

    Well, this is Fido we're talking about :-))

    Regards,
    Martin

    --- OpenXP 5.0.43
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)
  • From August Abolins@2:221/360 to Martin Foster on Sat Feb 1 17:46:52 2020
    On 01/02/2020 4:14 a.m., Martin Foster : August Abolins wrote:

     AA> +----------------------------------------------------------------
     AA> | Nodelist says: No requests at this BBS. Try requesting, anyway?
     AA> |                                                                
    AA> | >> Yes <    No                                        Â Â Â Â Â Â Â Â Â 
     AA> +----------------------------------------------------------------


    Yes it does and I've always regarded that as a nice feature

    It is nice to see a developer/designer to actually utilize the nodelist
    flags to produce something meaningful and informative to the user.


    Some SysOps don't always keep their nodelist file request flags
    up to date.

    And, one of the biggest file managing bbses out there doesn't even fly
    any of the Xn flags at all. :(

    Incidentally, when I freq that system, it drops the point designation in
    the acknowledgement and changes the zone number from 2 to 1.

    I wonder if you can reproduce it.

    It's probably just one of those "yeah.. it's old software" reasons at
    the freq server, and one just has to live with it.

    I'll send you the particulars in netmail.


    --
    Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc

    --- TB68/Win7 (just keeping things short!)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Martin Foster@2:310/31.3 to August Abolins on Sun Feb 9 11:40:00 2020
    Hello August!

    *** 01.02.20 at 17:48, August Abolins wrote to Martin Foster:

    [snip]
    It is nice to see a developer/designer to actually utilize the nodelist flags to produce something meaningful and informative to the user.

    Yes, it's very refreshing :)

    Some SysOps don't always keep their nodelist file request flags
    up to date.

    And, one of the biggest file managing bbses out there doesn't even fly
    any of the Xn flags at all. :(

    Incidentally, when I freq that system, it drops the point designation in the acknowledgement and changes the zone number from 2 to 1.

    I wonder if you can reproduce it.

    I actually reproduced it a long time ago but at the time, I just dismissed
    it as being a bit "sloppy".

    Regards,
    Martin

    --- OpenXP 5.0.43
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)