• Read only echos for FTN nodes.

    From Alter Ego@VERT/ALTERANT to All on Friday, January 31, 2020 16:19:45
    Howdy,

    Is there a way to make an echo "read only" for a downstream node?

    IE: They receive echomail that is posted, but any received mail from them is dropped (with an appropriate log) in sbbsecho?

    How about the reverse? IE: Mail can be received from a downstream node, but mail will not be exported to them?
    ...deon


    ... Think like a man of action, act like a man of thought.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to Alter Ego on Thursday, January 30, 2020 21:49:20
    Re: Read only echos for FTN nodes.
    By: Alter Ego to All on Fri Jan 31 2020 04:19 pm

    Howdy,

    Is there a way to make an echo "read only" for a downstream node?

    Not currently. Perhaps if you described the use-case more, I could consider how difficult or simple that would be to support. Like, do you want to disallow *any* echomail posts from a specific linked-node, or only for specific areas?

    IE: They receive echomail that is posted, but any received mail from them is dropped (with an appropriate log) in sbbsecho?

    How about the reverse? IE: Mail can be received from a downstream node, but mail will not be exported to them?

    Kind of. If you disable "secure echomail" in SBBSecho, then any linked node could post in any echo/area even if they're not linked to that specific area in the area file. It's a global setting however and normally suggested to be left "on" (disallow posts from noded in non-linked areas).

    digital man

    Synchronet/BBS Terminology Definition #63:
    SIGHUP = Hangup signal sent to a process when its controlling terminal is closed
    Norco, CA WX: 62.4F, 27.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alter Ego@VERT/ALTERANT to Digital Man on Friday, January 31, 2020 18:12:08
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Thu Jan 30 2020 09:49 pm

    Is there a way to make an echo "read only" for a downstream node?
    Not currently. Perhaps if you described the use-case more, I could consider how difficult or simple that would be to support. Like, do you want to disallow *any* echomail posts from a specific linked-node, or only for specific areas?

    The use case is to select which downstream FTN nodes cannot post to specific echoareas. (MBSE and I think Mystic ? can do this by assigning if a node can be sent messages or if messages could be received by that node.)

    I'm using echomail to send bot messages, so for specific echomails I want to use it like "broadcasting" - ie: a message posted in specific sub gets sent to a list of subscribers (FTN nodes).

    I dont want to receive any updates from those subscribers. (And I'm aware I could get a bot to trawl through the message base a delete "foreign" messages - but I thought if I could make it "read only" then I wouldnt need to. :)

    There may be a case as well to allow a downstream node receive echomail but deny them from posting to it. (And if they did, the posts would be localised to that node and whoever it fed.)

    For the reverse, I know I could use "netmail" instead of echomail - but like MBSE, where you can mark nodes as "Receive" nodes it achieves that goal in echomail.

    Anyway just a nice idea if it was there...


    ...deon


    ... Anyone who lives within his means suffers from a lack of imagination.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to Alter Ego on Friday, January 31, 2020 00:01:08
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Fri Jan 31 2020 06:12 pm

    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Thu Jan 30 2020 09:49 pm

    Is there a way to make an echo "read only" for a downstream node?
    Not currently. Perhaps if you described the use-case more, I could consider how difficult or simple that would be to support. Like, do you want to disallow *any* echomail posts from a specific linked-node, or only for specific areas?

    The use case is to select which downstream FTN nodes cannot post to specific echoareas.

    By use-case, I mean "for what purpose?"

    (MBSE and I think Mystic ? can do this by assigning if a node can
    be sent messages or if messages could be received by that node.)

    Yeah, don't have separate read and write access for a node to a msg area. The node either has access or it doesn't and access means both read and write.

    I'm using echomail to send bot messages, so for specific echomails I want to use it like "broadcasting" - ie: a message posted in specific sub gets sent to a list of subscribers (FTN nodes).

    I dont want to receive any updates from those subscribers. (And I'm aware I could get a bot to trawl through the message base a delete "foreign" messages - but I thought if I could make it "read only" then I wouldnt need to. :)

    So... you don't want to receive any messages whatsoever from "those subscribers" or only messages in specific message areas (implying that you *do* want to received messages from those subsribers in other message areas)?

    There may be a case as well to allow a downstream node receive echomail but deny them from posting to it. (And if they did, the posts would be localised to that node and whoever it fed.)

    I don't follow the parenthetical statement.

    For the reverse, I know I could use "netmail" instead of echomail - but like MBSE, where you can mark nodes as "Receive" nodes it achieves that goal in echomail.

    Anyway just a nice idea if it was there...

    It would be pretty easy to add a flag to mark a node as being "read only" (have no posting permissions in any echoes), but that's the end of "easy". Extending Access requirement strings (e.g. "Posting Requirements" in SCFG) to specify lists of fidonet nodes gets pretty ugly pretty quick. And AR strings are of limited length, so that'd quickly limit the number of nodes you could opt in or out. And of course, none of this is reflected in the areas.bbs file format.

    digital man

    This Is Spinal Tap quote #23:
    David St. Hubbins: I envy us.
    Norco, CA WX: 63.0F, 29.0% humidity, 2 mph WSW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Oli@VERT to Digital Man on Friday, January 31, 2020 11:40:28
    It would be pretty easy to add a flag to mark a node as being
    "read only" (have no posting permissions in any echoes), but
    that's the end of "easy". Extending Access requirement strings
    (e.g. "Posting Requirements" in SCFG) to specify lists of
    fidonet nodes gets pretty ugly pretty quick. And AR strings are
    of limited length, so that'd quickly limit the number of nodes
    you could opt in or out. And of course, none of this is
    reflected in the areas.bbs file format.

    What about making an area read-only with write-access for one node or only a few (let's say 3 or less)?

    I don't know the internals of synchronet, so maybe it's still not easy or pretty to implement.

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: kakistocracy (2:280/464.47)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Digital Man on Friday, January 31, 2020 08:00:48
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Thu Jan 30 2020 21:49:20


    Is there a way to make an echo "read only" for a downstream node?

    Not currently. Perhaps if you described the use-case more, I could consider how difficult or simple that would be to support. Like, do
    you want to disallow *any* echomail posts from a specific linked-node,
    or only for specific areas?

    as a mail hub, we generally use this capability to restrict postings in specific areas where the moderator has issued a ban for a system in their echo(s) because of either the sysop or one/some of the system users being moderated...

    then there's also read-only areas where postings are allowed only from certain systems... policy-wise in some networks, unauthorized posts in read-only or restricted access areas should be bounced back to the poster, preferably via netmail if FTN, private mail if QWK, or email if some other (eg: news), with an explanation for the rejection... i think i would only worry about FTN and QWK areas for now if i were to try to code up something for this...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Rampage@VERT/SESTAR to Digital Man on Friday, January 31, 2020 08:04:42
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Fri Jan 31 2020 00:01:08


    (MBSE and I think Mystic ? can do this by assigning if a node can
    be sent messages or if messages could be received by that node.)

    Yeah, don't have separate read and write access for a node to a msg
    area. The node either has access or it doesn't and access means both
    read and write.

    traditional ""advanced"" FTN tossers have this capability... i've used it numerous times in the past when i was running fastecho... i know there are numerous other FTN tossers that also offer it...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Digital Man@VERT to Oli on Friday, January 31, 2020 10:29:05
    Re: Read only echos for FTN nodes.
    By: Oli to Digital Man on Fri Jan 31 2020 11:40 am


    It would be pretty easy to add a flag to mark a node as being
    "read only" (have no posting permissions in any echoes), but
    that's the end of "easy". Extending Access requirement strings
    (e.g. "Posting Requirements" in SCFG) to specify lists of
    fidonet nodes gets pretty ugly pretty quick. And AR strings are
    of limited length, so that'd quickly limit the number of nodes
    you could opt in or out. And of course, none of this is
    reflected in the areas.bbs file format.

    What about making an area read-only with write-access for one node or only a few (let's say 3 or less)?

    I don't know the internals of synchronet, so maybe it's still not easy or pretty to implement.

    Right now, there is no way to attach posting requirements to fidonet nodes and no easy path to do that. Is this Alter Ego?

    digital man

    Synchronet/BBS Terminology Definition #32:
    FTS = FidoNet Technical Standard
    Norco, CA WX: 73.2F, 23.0% humidity, 3 mph SW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Rampage on Friday, January 31, 2020 10:39:52
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Fri Jan 31 2020 08:04 am

    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Fri Jan 31 2020 00:01:08


    (MBSE and I think Mystic ? can do this by assigning if a node can
    be sent messages or if messages could be received by that node.)

    Yeah, don't have separate read and write access for a node to a msg area. The node either has access or it doesn't and access means both read and write.

    traditional ""advanced"" FTN tossers have this capability... i've used it numerous times in the past when i was running fastecho... i know there are numerous other FTN tossers that also offer it...

    And this capability is reflected in their area file (e.g. areas.bbs) or some other configuration?

    digital man

    Synchronet/BBS Terminology Definition #70:
    SyncEdit = A defunct 3rd party full-screen editor written for Synchronet
    Norco, CA WX: 73.2F, 23.0% humidity, 3 mph SW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Oli@VERT to Digital Man on Friday, January 31, 2020 20:21:16
    traditional ""advanced"" FTN tossers have this capability... i've used it
    numerous times in the past when i was running fastecho... i know there are
    numerous other FTN tossers that also offer it...

    And this capability is reflected in their area file (e.g. areas.bbs) or
    some other
    configuration?

    In crashmail (and magimail) it is set in the main config file (crashmail.prefs).

    squish supports areas.bbs, but you have to define an area in squish.cfg, if you
    want to set an read-only flag.

    My uplink uses fmail. The area list in Areafix includes some read-only areas, so I guess fmail supports that too. It has a seperate config tool (TUI Or GUI),
    so maybe the area settings are stored in a binary config file.



    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: kakistocracy (2:280/464.47)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alter Ego@VERT/ALTERANT to Digital Man on Saturday, February 01, 2020 08:29:09
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Fri Jan 31 2020 08:00 am

    as a mail hub, we generally use this capability to restrict postings in specific areas where the moderator has issued a ban for a system in their echo(s) because of either the sysop or one/some of the system users being moderated...

    then there's also read-only areas where postings are allowed only from certain systems... policy-wise in some networks, unauthorized posts in read-only or restricted access areas should be bounced back to the poster, preferably via netmail if FTN, private mail if QWK, or email if some other (eg: news), with an explanation for the rejection... i think i would only worry about FTN and QWK areas for now if i were to try to code up something for this...

    I don't follow the parenthetical statement.

    This was my parenthetical scenario I was alluding to.
    ...deon


    ... The OFFICIAL tagline of the 1996 Olympics!

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Alter Ego@VERT/ALTERANT to Digital Man on Saturday, February 01, 2020 08:31:12
    Re: Read only echos for FTN nodes.
    By: Digital Man to Oli on Fri Jan 31 2020 10:29 am

    By: Oli to Digital Man on Fri Jan 31 2020 11:40 am
    Right now, there is no way to attach posting requirements to fidonet nodes and no easy path to do that. Is this Alter Ego?

    Nope, I'm not Oli - he's another dude...
    ...deon


    ... A man's only as old as the woman he feels.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Alter Ego@VERT/ALTERANT to Digital Man on Saturday, February 01, 2020 08:35:36
    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Fri Jan 31 2020 10:39 am

    And this capability is reflected in their area file (e.g. areas.bbs) or some other configuration?

    I'm not sure where MBSE stores the config, but I imagine its in an internal DB like structure...

    Each area has a list of nodes (much like areas.bbs, where you list the nodes that can import/export from). However, with each node, you can assign them "receive" or "send" ability - aka, import from or export to.

    The result is the echo can be considered read only (send only, but receives are dropped), or receive only (dont export to it, but happily receive from it).

    I think it would be a nice add to SBBS if this level of control was available as well. (And I would use it for a project I'm playing with, not necessarily to apply or enforce a policy to a downstream BBS/echomail system).
    ...deon


    ... Illiteratets of the wlord. Untie!

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to Alter Ego on Friday, January 31, 2020 15:37:10
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Sat Feb 01 2020 08:35 am

    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Fri Jan 31 2020 10:39 am

    And this capability is reflected in their area file (e.g. areas.bbs) or some other configuration?

    I'm not sure where MBSE stores the config, but I imagine its in an internal DB like structure...

    I just wanted to be sure there wasn't some areas.bbs derivative out there that I didn't know about.

    Each area has a list of nodes (much like areas.bbs, where you list the nodes that can import/export from). However, with each node, you can assign them "receive" or "send" ability - aka, import from or export to.

    It seems to me to be a pretty strange scenario where you'd have an area in which you wanted to allow a node to post messages, but not to receive any.

    The result is the echo can be considered read only (send only, but receives are dropped), or receive only (dont export to it, but happily receive from it).

    Yeah, receive-only, I don't get. Even in SBBS/SCFG where you have a lot of flexiblity with regards to access requirements, you can't have a message area that a user can post to, but not read any messages in that area (including their own).

    I think it would be a nice add to SBBS if this level of control was available as well. (And I would use it for a project I'm playing with, not necessarily to apply or enforce a policy to a downstream BBS/echomail system).

    You have more flexibility/configurability for QWK networking. Have you considered using QWKnet instead?

    digital man

    Synchronet "Real Fact" #62:
    Name of Synchronet PCMS compiler/language "Baja" was coined by Michael Swindell.
    Norco, CA WX: 79.0F, 18.0% humidity, 2 mph SSE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Digital Man on Friday, January 31, 2020 20:38:36
    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Fri Jan 31 2020 10:39:52


    Yeah, don't have separate read and write access for a node to a msg
    area. The node either has access or it doesn't and access means
    both read and write.

    traditional ""advanced"" FTN tossers have this capability... i've
    used it numerous times in the past when i was running fastecho...
    i know there are numerous other FTN tossers that also offer it...

    And this capability is reflected in their area file (e.g. areas.bbs)
    or some other configuration?

    there's no mechanism for denoting it in the areas.bbs file... it is only in the record for the linked node and/or the message area... basically similar to the method currently used to limit access to areas but applied on a read/write level instead of an overall level... FE did it with secutiry levels which worked but was limiting in several ways...

    i'll try to post some screen shots from the FE docs... the character set conversion might be a tad off because the editor (kate) that i'm using only let's me use CP850 to get the best view of the >128 characters so there's going to be some manual editing to clean it up into ASCII because i have no clue if the proper bytes will be pasted for proper UTF-8 glyphs :(

    the following system has access to echo groups A and B and has security setting 100...


    FESetup System Data Export Import F1 Help

    +== 1/1 =================== Node-Manager ==========================+
    | Addresses |
    | Main: 2:999/900.0 4D/Type 2+: Y |
    | ARCmail: 2:999/900.0 TosScan: N |
    | ARCmail 0.60: N |
    | Name: Ben Grimm Pack priority: 0 |
    | Convert Umlaut: N |
    | Your Aka: 2:999/999.0 |
    | Allow Area-Create: Y |
    | Passwords New Area Default Group: B |
    | Packet: Export By Name: N |
    | AreaFix: THETHING |
    | Status AreaFix flags: > |
    | ARCmail: None |
    | AreaFix: None Send Notify: Y |
    | Packer: ZIP Max. size: 0 Send Help: Y |
    | |
    | Groups: AB Passive: N |
    | Security: 100 Automatic Passive: 0 |
    +==================================================================+ Enter-Edit Ins-Add Del-Delete F2-Rout F5-Browse F4 Area List F5-Copy

    [...]

    5.5.1.8 - Groups

    In the group section you have to define the groups of areas that
    your downlink will be able to request to your system through an AreaFix
    request. The same groups will be used by FastEcho internally for its
    maintenance. When you position the cursor upon the "Groups" item then
    the following PopUp-menu will be automatically shown:

    +---------------------------------+
    |>_ A) - FidoNet EchoMail Natl< |
    | _ B) - FidoNet EchoMail Intl |
    | C) - ZyXELnet EchoMail Area |
    | D) - Local BBS Area |
    | [...] |
    | X) |
    | Y) |
    | Z) |
    +---------------------------------+

    The groups listed in this box are the same you defined before in
    the "Group Names" section (see: 5.4.13 paragraph). Here, you must se-
    lect, by marking them, the areas-group that you want left available to
    the downlink which you are defining. This downlink, then, will be able
    to link or unlink the available areas sending an AreaFix request to
    your system. You can, of course, activate manually other areas belon-
    ging to other groups but the operating field of your downlink will be
    strictly limited to the group defined herein. To activate the groups,
    simply move the cursor upon the desired group that you want to make ac-
    tive for this downlink and press the space key; you will see one small
    black square to the left of the selected group name. This box means
    that the group will be available for this node. To select groups you
    may either press the relative key (I.E. pressing the "A" key you will
    tag the "A" group), further, you can select all groups with the "ALT-A"
    key combination or deselect them with "ALT-C". You might know that
    there are some exceptions to this rule, for example, if your downlink
    has a security level of 10 and has the "A" group available, but you,
    have a particular area belonging to the "A" group that has a minimum
    security level of 20, then your downlink won't be able to link this
    area because its security level isn't enough. For our tutorial you
    haven't any need to define groups for this node because you are confi-
    guring one "Uplink" and you will never receive an AreaFix request from
    an "Uplink" but, for "Equity" you'll tag it all the same. Press the
    letter "A" and the letter "B" until the two fidonet groups are tagged
    by the little black square; then press the "ESC" key to return to the
    "Node Configuration" layout.

    5.5.1.9 - Security

    As already mentioned in the previous paragraph, a downlink cannot
    link any areas having security level higher that the one specified in
    this field; further, this security level, is strictly related to the
    groups available to this node. For example: A node has level 10 and has
    available the "A" and the "B" groups; this node will request, by means
    of AreaFix, an EchoMail area belonging to group "A" but having security
    level 11, well, the linking will be denied because of its level; the
    same node now wants to link, with AreaFix request, an EchoMail area be-
    longing to the group "C", the linking will be denied again because this

    -----------------------------------------------------------------------
    - 50 -
    FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
    -----------------------------------------------------------------------

    node hasn't any access to group "C". A node can definitely link or un-
    link any areas IF the area belongs to an authorized group and it has a
    security level lower or equal to the Node security level. For the tu-
    torial, input here the level 100 and strike the "return" key.



    then we have the defaults for the message area groups...



    FESetup System Data Export Import F1 Help
    +--------------------- Area defaults for Group A --------------------+
    | Comment: FidoNet EchoMail Natl |
    | Origin: System in test @Fidonet.org |
    | Type: EchoMail |
    | Storage: Hudson Board: 1 |
    | Path: |
    | Use Aka: 2:999/999.0 |
    | |
    | Mandatory: N Keep SEEN-BY: Y Tiny SEEN-BY: N CPD: N |
    | Convert Umlaut: N Keep users: N Kill read: N Disab. Psve: N |
    | Remote changes: Y Hide area: N Keep NetMail: N |
    | |
    | Purging # Msgs: 50 # Days: 30 # Rcvd Days: 0 |
    | Security Read: 0 Write: 0 |
    | |
    | SEEN-BY: 2:999/999.0 |
    | Export to: 2:999/900 |
    +--------------------------------------------------------------------+
    Press F10 to save or ESC to abort editing...



    so the defaults for message group A have security of 0 for both read and write access... the defaults for this group are what an area in this group starts with...

    now an area definition...



    +------------------------------ Edit Area ---------------------------+
    | Name: Group: |
    | Comment: |
    | Origin: |
    | Type: EchoMail |
    | Storage: Hudson Board: |
    | Path: |
    | Use Aka: |
    | |
    | Mandatory: N Keep SEEN-BY: N Tiny SEEN-BY: N CPD: N Psive: N |
    | Convert Umlaut: N Keep users: N Kill read: N Disble Psive: N |
    | Remote changes: Y Hide area: N Keep NetMail: N |
    | |
    | Purging # Msgs: 0 # Days: 0 # Rcvd Days: 0 |
    | Security Read: 0 Write: 0 |
    | |
    | SEEN-BY: |
    | Export to: | +--------------------------------------------------------------------+
    |Press F10 to save or ESC to abort editing... | +--------------------------------------------------------------------+

    [...]

    5.5.3.1.23 - Security

    In the following two items you can define which security level the
    area you are defining will have. The levels must be adjusted conformly
    to the security level that the nodes, defined in your "Node Manager",
    have, in order to allow them to link this particular area or not.
    These security levels have only means for automated operations
    performed from your downlinks through AreaFix "Link" requests and
    whether or not messages in an area will be accepted from or send to a
    specific system.

    5.5.3.1.23.1 - Read (Security)

    This is the security level that you wish to assign to this area.
    If a downlink, having its own security level in node manager (see: Se-
    curity - chapter 5.5.1.9) greater or, at least, equal to this "Read-
    area-security", tries to link this area, its request will be honored;
    if, instead, it has the security level lower than the one specified in
    this item, then the request will be refused and the link denied. Remem-
    ber that this switch gives to the downlinks, only the permission to
    read this area. In this way you may leave some downlinks abled to Read
    only this area even if they are currently linked. For this tutorial,
    input in this field the number "10" and strike return to continue.

    5.5.3.1.23.2 - Write (Security)

    With this item you can bind the "Write-Security" at this particular
    area. As said before, a downlink may have the permission to "read-on-
    ly" a area if its node-security level is greater or equal only to the
    one specified in "Read" security. If you want to leave the downlinks
    also free to link this area in "Write", check that the "Node" se-
    curity level is greater or, at least, equal to the "Area" security le-
    vel you will input herein. For our tutorial, input the number "10" con-
    firming with the "return" key.

    5.5.3.1.23.3 - Examples (Security)

    The node 2:888/888 has security level 100
    The node 2:777/777 has security level 50
    The node 2:666/666 has security level 30
    The EchoMail area TEST0.CHT has security level 100 read and 100 write
    The EchoMail area TEST1.CHT has security level 50 read and 50 write
    The EchoMail area TEST2.CHT has security level 30 read and 40 write

    The node 2:888/888 will be able to link all the EchoMail areas here
    mentioned both in read/write because it has 100 as security level which
    is higher than the area security level for TEST1 and TEST2 and equal to
    the TEST0 read/write level. The node 2:777/777 will be able to link
    only the TEST1 and TEST2 EchoMail area, because its security level is
    greater than the read/write security level of the TEST2 area and equal
    to the TEST1 read/write level. The node 2:666/666 will be able to link
    in read-only the EchoMail area TEST2 because its security level is lo-
    wer than the read/write security level of the TEST0 and TEST1 area and
    furthermore, is lower that the "write" security level of the TEST2.


    it worked but even reading over it now, i see the limitations and i'm sure there's probably easier and better ways to handle these types of needs/desires... in any case, a linked system has to have access to the group and then the security level for read and write determines if messages are sent to or received from that system...

    sorry, that's longer than i really wanted to post but after having done it now, i don't want to take a chance to edit it down for fear that fseditor will ABEND on me and show the dreaded "the impossible has happened" message...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Rampage@VERT/SESTAR to Digital Man on Friday, January 31, 2020 20:47:37
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Fri Jan 31 2020 15:37:10


    It seems to me to be a pretty strange scenario where you'd have an
    area in which you wanted to allow a node to post messages, but not
    to receive any.

    consider an information only area where only one system posts the information and all other systems are supposed to be read-only... in cases where some systems use tossers that cannot restrict read/write access, the originating system doesn't want any posts from them coming back into the information area... so those systems are set for read-only and those unwanted posts are dropped into the bitbucket... those posts can be dropped earlier if other systems downstream from the originating system also have read/write access permission capabilities...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Digital Man@VERT to Rampage on Friday, January 31, 2020 18:10:06
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Fri Jan 31 2020 08:38 pm

    or some other configuration?

    there's no mechanism for denoting it in the areas.bbs file... it is only in the record for the linked node and/or the message area... basically similar to the method currently used to limit access to areas but applied on a read/write level instead of an overall level... FE did it with secutiry levels which worked but was limiting in several ways...

    ...

    sorry, that's longer than i really wanted to post but after having done it now, i don't want to take a chance to edit it down for fear that fseditor will ABEND on me and show the dreaded "the impossible has happened" message...

    No, that was helpful. It did not appear that FE supports the concept of a "write-only" access however (where a node can write, but not read an area). I'm not too eager to try to support that type of configuration either.

    digital man

    Synchronet/BBS Terminology Definition #64:
    SMB = Synchronet Message Base (e.g. smblib)
    Norco, CA WX: 70.3F, 24.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Rampage on Friday, January 31, 2020 18:12:44
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Fri Jan 31 2020 08:47 pm

    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Fri Jan 31 2020 15:37:10


    It seems to me to be a pretty strange scenario where you'd have an
    area in which you wanted to allow a node to post messages, but not
    to receive any.

    consider an information only area where only one system posts the information and all other systems are supposed to be read-only... in cases where some systems use tossers that cannot restrict read/write access, the originating system doesn't want any posts from them coming back into the information area... so those systems are set for read-only and those unwanted posts are dropped into the bitbucket... those posts can be dropped earlier if other systems downstream from the originating system also have read/write access permission capabilities...

    What you're describing sounds like a read-only area, like the "Synchronet Announcements" area in DOVE-Net. This configuration works fine by simply denying write accesss to all the nodes (the hub, VERT, is the only allowed "writer").

    I still don't see a need for a "write-only" area.

    digital man

    This Is Spinal Tap quote #3:
    How much more black could this be? and the answer is none. None more black. Norco, CA WX: 69.4F, 25.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Al@VERT/TRMB to Digital Man on Saturday, February 01, 2020 05:06:00
    What you're describing sounds like a read-only area, like the
    "Synchronet Announcements" area in DOVE-Net. This configuration
    works fine by simply denying write accesss to all the nodes (the
    hub, VERT, is the only allowed "writer").

    I think that's what it is, but for FTN areas.

    I still don't see a need for a "write-only" area.

    HPT has a "level <integer>" keyword that can be used in the nodes section
    of the config and you can use -lr <integer> and -lw <integer> in the
    echoarea lines of the config to do this.

    None of those options are used in my config since it hasn't come up in my setup, but I could do that if it ever did.

    Ttyl :-),
    Al

    ---
    * MagickaBBS * The Rusty MailBox - Penticton, BC Canada
  • From Alter Ego@VERT/ALTERANT to Digital Man on Saturday, February 01, 2020 16:02:50
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Fri Jan 31 2020 03:37 pm

    It seems to me to be a pretty strange scenario where you'd have an area in which you wanted to allow a node to post messages, but not to receive any.

    I think you are right - it probably has less value or usage than the opposite (aka read only echos) - but the implementation on other BBS software (well MBSE and I dont recall if mystic can) does enable that scenario.

    I may use it in my use case though if it was there.

    I'm playing with videotex frames, and the idea a downstream system can author pages within an authorised prefix (eg *642...). My "edit frame" routines will result in the frame being posted as an echomail message (like you do with sbbslist, etc), which the master machine will receive, validate the system is authorised on that page prefix, and then blast it out for "other nodes" to receive.

    The automation that posts the message to the echomail message area would never consider that messages received in that area need to be processed - hence no reason to export to it.

    (And if its not clear, people dont need to read these messages, jsexec <tool> will.)

    You have more flexibility/configurability for QWK networking. Have you considered using QWKnet instead?

    I havent. I know FTN better than QWKnet...
    ...deon


    ... God can't alter history, so he created historians.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Alter Ego@VERT/ALTERANT to Digital Man on Saturday, February 01, 2020 16:19:14
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Sat Feb 01 2020 04:02 pm

    I may use it in my use case though if it was there.

    I want to re-iterate as well - I did mention it in my first message.

    For "write-only", I can achieve that functionality with netmail - which I'm happy to do. I sense you are not inclined to implement that functionality specificially (I get it) - and I was only indicating how MBSE does it in case you wanted to alter sbbsecho to function in a similar way.

    The "read-only" is more desirable and I think has more valuable for the greater community. If you would consider implementing it, great, if not I'll just have my "jsxec <function>" read through messages and delete whatever it doesnt like to see.
    ...deon


    ... Everybody is somebody else's weirdo.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Rampage@VERT/SESTAR to Digital Man on Saturday, February 01, 2020 06:09:31
    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Fri Jan 31 2020 18:12:44


    What you're describing sounds like a read-only area, like the
    "Synchronet Announcements" area in DOVE-Net.

    correct...

    This configuration works fine by simply denying write accesss
    to all the nodes (the hub, VERT, is the only allowed "writer").

    true, again... this makes VERT "write only" as well, doesn't it? since it writes and doesn't allow other systems posts? maybe it is actually the same side of the coin? now that i think about it and have had some sleep plus c0ffee, it makes sense LUL


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Oli@VERT to Digital Man on Saturday, February 01, 2020 17:56:24
    31 Jan 20 18:12, you wrote to Rampage:

    I still don't see a need for a "write-only" area.

    I used write-only in Crashmail for switching from one hub to another or getting
    an echo from two hubs. I don't know if it really made any difference, I just used this option, because it was available and I thought it might reduce the chances for dupes.

    Maybe it could be useful in a meshed routing setup, if some problems arise and you want to stear the mail-flow in a specific direction. Maybe there are some other use cases for echomail routing or maybe some authors just added it out of
    habbit, because if you have read-only there has to be write-only too. I don't know, but I would love to hear some real uses cases for it :).

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: kakistocracy (2:280/464.47)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Rampage on Saturday, February 01, 2020 13:21:20
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Sat Feb 01 2020 06:09 am

    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Fri Jan 31 2020 18:12:44


    What you're describing sounds like a read-only area, like the "Synchronet Announcements" area in DOVE-Net.

    correct...

    This configuration works fine by simply denying write accesss
    to all the nodes (the hub, VERT, is the only allowed "writer").

    true, again... this makes VERT "write only" as well, doesn't it? since it writes and doesn't allow other systems posts?

    No, becaue "VERT" would not be represented in the network configuration (e.g. area file, if I were using FTN) since VERT is the local system. I don't have my *own* FTN addresses listed in the areas.bbs file.

    digital man

    Synchronet "Real Fact" #33:
    The Synchronet web user interface was contributed by Robert Couture, Runemaster.
    Norco, CA WX: 83.4F, 19.0% humidity, 3 mph SW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Alter Ego on Saturday, February 01, 2020 18:14:49
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Sat Feb 01 2020 04:19 pm

    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Sat Feb 01 2020 04:02 pm

    I may use it in my use case though if it was there.

    I want to re-iterate as well - I did mention it in my first message.

    For "write-only", I can achieve that functionality with netmail - which I'm happy to do. I sense you are not inclined to implement that functionality specificially (I get it) - and I was only indicating how MBSE does it in case you wanted to alter sbbsecho to function in a similar way.

    The "read-only" is more desirable and I think has more valuable for the greater community. If you would consider implementing it, great, if not I'll just have my "jsxec <function>" read through messages and delete whatever it doesnt like to see.

    How about a setting in SCFG->Message Areas ... Sub-board->Network Options where you could set FidoNet to be read-only, write-only, or read/write (the default)? It would be a global setting, so it would apply to all your links in SBBSecho (that are linked with that sub). Would that meet your needs?

    digital man

    Synchronet/BBS Terminology Definition #79:
    UDP = User Datagram Protocol
    Norco, CA WX: 74.7F, 28.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alter Ego@VERT/ALTERANT to Digital Man on Sunday, February 02, 2020 16:14:44
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Sat Feb 01 2020 06:14 pm

    How about a setting in SCFG->Message Areas ... Sub-board->Network Options where you could set FidoNet to be read-only, write-only, or read/write (the default)? It would be a global setting, so it would apply to all your links in SBBSecho (that are linked with that sub). Would that meet your needs?

    As a global setting, it would probably be OK - but I think the better implementation would be granular configuration by the sysop - ie: by echoarea, defining which exported nodes can receive, and which nodes we are prepared to receive from.

    As an idea, in areas.bbs, perhaps it could be implemented as simply as:

    ECHO_TAG -1:1/1 +1:1/2 1:1/3

    where:
    * 1:1/1 will export to, but import from rejected
    * 1:1/2 will not export to, but import from will be accepted
    * 1:1/3 will export to, and receive from

    This could be complemented with +|-ECHO_TAG, where a plus infront of it would be anybody subscribing to this area would subscribed with "+" (wont export to/import accepted), a minus in front would be subscribed with "-" (export to, but receive rejected) and nothing export to and receive from.

    Howz that for an idea?
    ...deon


    ... The deceased should be preserved by electroplating them.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Paul Quinn@VERT to Alter Ego on Sunday, February 02, 2020 15:34:22
    Hi! Alter,

    On 02 Feb 20 16:14, you wrote to Digital Man:

    Howz that for an idea?

    It nearly made me spew. There are more packages that read areas.bbs files than
    Syncro. E.g. Fmail/lnx (and therefore also Windows versions) would barf. Without the current standard form I wouldn't be able to feed Fmail/lnx new (area) pathnames. Most/many other BBS or tosser programs would be screwed as well.

    Cheers,
    Paul.

    ... Trees moving back and forth are what make the wind blow.
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alter Ego@VERT/ALTERANT to Paul Quinn on Sunday, February 02, 2020 20:05:18
    Re: Read only echos for FTN nodes.
    By: Paul Quinn to Alter Ego on Sun Feb 02 2020 03:34 pm

    Howz that for an idea?
    It nearly made me spew. There are more packages that read areas.bbs files

    Wow, what a reaction.

    I get the point, bad idea because other systems depend on areas.bbs.
    ...deon


    ... The writer does the most who gives the reader the most

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to Alter Ego on Sunday, February 02, 2020 12:10:48
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Sun Feb 02 2020 04:14 pm

    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Sat Feb 01 2020 06:14 pm

    How about a setting in SCFG->Message Areas ... Sub-board->Network Options where you could set FidoNet to be read-only, write-only, or read/write (the default)? It would be a global setting, so it would apply to all your links in SBBSecho (that are linked with that sub). Would that meet your needs?

    As a global setting, it would probably be OK

    It certainly woudl be easier.

    - but I think the better
    implementation would be granular configuration by the sysop - ie: by echoarea, defining which exported nodes can receive, and which nodes we are prepared to receive from.

    As an idea, in areas.bbs, perhaps it could be implemented as simply as:

    ECHO_TAG -1:1/1 +1:1/2 1:1/3

    where:
    * 1:1/1 will export to, but import from rejected
    * 1:1/2 will not export to, but import from will be accepted
    * 1:1/3 will export to, and receive from

    This could be complemented with +|-ECHO_TAG, where a plus infront of it would be anybody subscribing to this area would subscribed with "+" (wont export to/import accepted), a minus in front would be subscribed with "-" (export to, but receive rejected) and nothing export to and receive from.

    Howz that for an idea?

    That was my first thought too. The problem is that nodes can add and remove themselves from the area file via areafix. The area manager wouldn't know to place a '+' or '-' in front of a node address when it was added via areafix.

    digital man

    Synchronet/BBS Terminology Definition #28:
    FREQ = File Request
    Norco, CA WX: 71.3F, 32.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alter Ego@VERT/ALTERANT to Digital Man on Monday, February 03, 2020 07:47:38
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Sun Feb 02 2020 12:10 pm

    That was my first thought too. The problem is that nodes can add and remove themselves from the area file via areafix. The area manager wouldn't know to place a '+' or '-' in front of a node address when it was added via areafix.

    That's why I thougth of prefixing the area name as well with + or -, which would set the defaults for nodes using areafix for that echotag. Naturally, the sysop should be able to admend it as appropriate.

    My idea was this would be backward compatible with systems that using areas.bbs - they continue to use it as is today (no pluses or minuses used). But for systems running SBBS, that want finer grained control over echos, then it adds that capability with (hopefully) little re-engineering..
    ...deon


    ... Preparation, knowledge, and discipline can deal with any form of danger.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Digital Man@VERT to Alter Ego on Sunday, February 02, 2020 13:45:56
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Mon Feb 03 2020 07:47 am

    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Sun Feb 02 2020 12:10 pm

    That was my first thought too. The problem is that nodes can add and remove themselves from the area file via areafix. The area manager wouldn't know to place a '+' or '-' in front of a node address when it was added via areafix.

    That's why I thougth of prefixing the area name as well with + or -, which would set the defaults for nodes using areafix for that echotag. Naturally, the sysop should be able to admend it as appropriate.

    Oh, I didn't notice that in your proposal.

    My idea was this would be backward compatible with systems that using areas.bbs - they continue to use it as is today (no pluses or minuses used). But for systems running SBBS, that want finer grained control over echos, then it adds that capability with (hopefully) little re-engineering..

    I'll probably just start with a global read/write-only setting for fido subs in SCFG. The AreaFix / area file stuff is already too fragile as it is.

    digital man

    This Is Spinal Tap quote #2:
    Nigel Tufnel: Well, this piece is called "Lick My Love Pump".
    Norco, CA WX: 71.6F, 47.0% humidity, 8 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Paul Quinn@VERT to Alter Ego on Monday, February 03, 2020 07:56:12
    Hi! Deon,

    On 02/02/2020 07:05 PM, you wrote:

    Howz that for an idea?
    It nearly made me spew. There are more packages that read
    areas.bbs files

    Wow, what a reaction.

    :)

    I get the point, bad idea because other systems depend on areas.bbs.

    Welcome to the FTSC. There may (or may not?) be a standard for the Areas.Bbs format but such things are fairly uniform, maybe as a result of developer "gentleman's agreement" over the last 25-30 years.

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Hey Look! It's the Wit brothers: Half, Dim and Nit. (3:640/1384.125)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Digital Man on Sunday, February 02, 2020 17:19:06
    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Sun Feb 02 2020 12:10:48


    That was my first thought too. The problem is that nodes can add
    and remove themselves from the area file via areafix. The area
    manager wouldn't know to place a '+' or '-' in front of a node
    address when it was added via areafix.

    it should know that information from the sbbsecho.ini file with the group tags and security levels ;)


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Rampage@VERT/SESTAR to Alter Ego on Sunday, February 02, 2020 17:23:14
    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Mon Feb 03 2020 07:47:38


    My idea was this would be backward compatible with systems that
    using areas.bbs - they continue to use it as is today (no pluses
    or minuses used). But for systems running SBBS, that want finer
    grained control over echos, then it adds that capability with
    (hopefully) little re-engineering..

    i'm not aware of any other tools that use sbbsecho's areas.bbs file... are you?

    the format is already different enough from the standard that this enhancement might be a possibility... sbbsecho and sbbs are the only two tools that i know of that use the areas.bbs file... maybe golded or other sysop message readers that specifically support the sbbs message area format but...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Rampage@VERT/SESTAR to Paul Quinn on Sunday, February 02, 2020 17:55:33
    Re: Read only echos for FTN nodes.
    By: Paul Quinn to Alter Ego on Mon Feb 03 2020 07:56:12


    I get the point, bad idea because other systems depend on areas.bbs.

    Welcome to the FTSC.

    it has nothing to do with the FTSC ;)

    There may (or may not?) be a standard for the Areas.Bbs format but
    such things are fairly uniform, maybe as a result of developer "gentleman's agreement" over the last 25-30 years.

    there is a psuedo standard, yes... programs that share the same areas.bbs file must adhere to the same format or there will be problems... if those programs' devs agree on a modified format, that's fine and it doesn't break anything... the areas.bbs file is a local configuration file and is not shared with other systems... i've worked on systems that had several areas.bbs files in different directories because the programs that used them had different formats... yes, it was troublesome to keep them synced but not too bad... the worst was systems that use only 2D (net/node only) addressing in the linked systems list while others used 3D/4D (z:n/n or n/n.p or z:n/n.p)... then 5D came along and some areas.bbs use the domains in the linked systems part of the lines as well...


    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Paul Quinn@VERT to Rampage on Monday, February 03, 2020 09:52:19
    Hi! mark,

    On 02/03/2020 08:55 AM, you wrote:

    I get the point, bad idea because other systems depend on areas.bbs.

    Welcome to the FTSC.
    it has nothing to do with the FTSC ;)

    Only that it is an example of 'the why' of having such a system/entity.

    there is a psuedo standard, yes...

    That much I knew. Thank you for helping. I have seen a few... very few.

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: The sound of a SysOp reading mail: <cr><cr><cr><cr> (3:640/1384.125)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Rampage on Sunday, February 02, 2020 16:24:39
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Sun Feb 02 2020 05:19 pm

    Re: Read only echos for FTN nodes.
    By: Digital Man to Alter Ego on Sun Feb 02 2020 12:10:48


    That was my first thought too. The problem is that nodes can add
    and remove themselves from the area file via areafix. The area
    manager wouldn't know to place a '+' or '-' in front of a node
    address when it was added via areafix.

    it should know that information from the sbbsecho.ini file with the group tags and security levels ;)

    None of that information exists in sbbsecho.ini, so yeah, but no. There is "per area" type configuration in sbbsecho.ini, currently, at least.

    digital man

    This Is Spinal Tap quote #28:
    We've got Armadillos in our trousers. It's really quite frightening.
    Norco, CA WX: 66.7F, 61.0% humidity, 6 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Rampage on Sunday, February 02, 2020 16:25:47
    Re: Read only echos for FTN nodes.
    By: Rampage to Alter Ego on Sun Feb 02 2020 05:23 pm

    Re: Read only echos for FTN nodes.
    By: Alter Ego to Digital Man on Mon Feb 03 2020 07:47:38


    My idea was this would be backward compatible with systems that
    using areas.bbs - they continue to use it as is today (no pluses
    or minuses used). But for systems running SBBS, that want finer
    grained control over echos, then it adds that capability with (hopefully) little re-engineering..

    i'm not aware of any other tools that use sbbsecho's areas.bbs file... are you?

    the format is already different enough from the standard that this enhancement might be a possibility... sbbsecho and sbbs are the only two tools that i know of that use the areas.bbs file...

    sbbs actually doesn't (just sbbsecho).

    maybe golded or other
    sysop message readers that specifically support the sbbs message area format but...

    I think GoldEd+ has support for Synchronet's msgs.cnf file to get area information. <shrug> Who knows about other utilities, but probably not.

    digital man

    Synchronet "Real Fact" #53:
    Synchronet Blackjack was the first multi-node/multi-user game for Synchronet. Norco, CA WX: 65.4F, 65.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Rampage on Sunday, February 02, 2020 16:27:47
    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Sun Feb 02 2020 04:24 pm

    None of that information exists in sbbsecho.ini, so yeah, but no. There is "per area" type configuration in sbbsecho.ini, currently, at least.

    There is "no per area" type configuration... I meant to say.

    digital man

    Synchronet/BBS Terminology Definition #10:
    C64 = Commodore 64 (personal computer)
    Norco, CA WX: 65.4F, 65.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From mark lewis@VERT to Digital Man on Sunday, February 02, 2020 19:40:29
    Re: Read only echos for FTN nodes.
    By: Digital Man to Rampage on Sun Feb 02 2020 16:24:39


    That was my first thought too. The problem is that nodes can add
    and remove themselves from the area file via areafix. The area
    manager wouldn't know to place a '+' or '-' in front of a node
    address when it was added via areafix.

    it should know that information from the sbbsecho.ini file with
    the group tags and security levels ;)

    None of that information exists in sbbsecho.ini, so yeah, but no.
    There is "per area" type configuration in sbbsecho.ini, currently,
    at least.

    yes, true... that information would exist i sbbsecho.ini if the enhancements being discussed were implemented and in place ;)


    )\/(ark
    --- SBBSecho 3.10-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Alter Ego@VERT/ALTERANT to Rampage on Monday, February 03, 2020 18:18:59
    Re: Read only echos for FTN nodes.
    By: Rampage to Alter Ego on Sun Feb 02 2020 05:23 pm

    i'm not aware of any other tools that use sbbsecho's areas.bbs file... are you?

    I'm not but Paul Quinn "nearly spewed" when I suggested it though :)

    So if there were, that would be OK though, because I'm not suggesting to "change it", but to enhance it, and the defaults would be no change as it is implemented today.
    ...deon


    ... When I was a little kid, we had a quicksand box. I was an only child eventually.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Alter Ego@VERT/ALTERANT to Rampage on Monday, February 03, 2020 18:21:30
    Re: Read only echos for FTN nodes.
    By: Rampage to Digital Man on Sun Feb 02 2020 05:19 pm

    it should know that information from the sbbsecho.ini file with the group tags and security levels ;)

    Even better (I think) :)
    ...deon


    ... Everywhere is within walking distance if you have the time.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Oli@VERT to Alter Ego on Monday, February 03, 2020 13:19:50
    03 Feb 20 18:18, you wrote to Rampage:

    i'm not aware of any other tools that use sbbsecho's areas.bbs file... are
    you?

    I'm not but Paul Quinn "nearly spewed" when I suggested it though :)

    So if there were, that would be OK though, because I'm not suggesting to
    "change
    it", but to enhance it, and the defaults would be no change as it is
    implemented
    today.

    It's also not that hard to convert different formats between each other. Even 25 years ago I didn't use areas.bbs files, because it was so limited.

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: kakistocracy (2:280/464.47)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net