[snip]
+ File bases now have a "File Echo Hub" flag which if set to Yes will
prevent any pass-through files for this file echo. If a new file for the
base is received via a TIC it will be added to the file base, but not sent
to any downlinks (unless manually hatched by the SysOp).
[snip]
Ideally I'm after an enhancement for this. As I want other fsxNet HUBs (e.g. 2/100, 3/100, 4/100) to be able to accept incoming files sent from a fellow 'trusted' HUB system like 1/100. For those files my wish is the 2/100, 3/100 and 4/100 hubs allow those files to be passed through to local nodes.
I really like the way things are at the moment if this setting is enabled as
it does negate nodes passing files though HUBs. But the problem it also now negates 'trusted' HUBs from sharing (for example) a nodelist and sending it
out to nodes.
Could there be a way of adding/removing trusted nodes from the list of
defined echomail nodes the HUB system knows of, and if added to the 'allowed' list for that file base, files sent by that node(s) would be allowed to pass?
So something that's more granular vs just all or nothing as it is now?
Best, Paul
--- Mystic BBS v1.12 A37 2017/12/23 (Windows/32)
* Origin: Agency BBS |
telnet://agency.bbs.geek.nz (21:1/101)