It's been nearly a year since we added a bunch of new echomail areas to fsxNet and I figure it's a good time to review which are worth retaining and which should be removed.
fsxNet and I figure it's a good time to review which are worth retaining and which should be removed.
fsxNet and I figure it's a good time to review which are worth retaining
and which should be removed.
I don't have any comment for or against any bases, but I have a question regarding how you would go about delisting one or more bases should you wish to. Is it as easy as deleting the message area from the hub(s) or do you need
to do something magical to stop people who may be subscribed from posting to them and recreating them?
This is something I have completely overlooked since starting my own network,
and I have just pondered the question, unable to come up with an answer myself
while reading your message.
Thanks in advance.
This is something I have completely overlooked since starting my own network, and I have just pondered the question, unable to come up with an answer myself while reading your message.
You should be able to do an AREAFIX to unlink any conference area with a minus sign in
front of the conference name.
One guesses that removal at the hub level will be sufficient, but I'm thinking of the good ol' days when everything was fully manual. If odd systems continue to post in those areas they'll just end up in the "bad" board.
Thanks Mike, but I was meaning from a network hub point of view, I run an echomail network and I was wondering how you would remove an echomail
base completely from a network so that no systems could accidentally recreate the base =)
I don't have any comment for or against any bases, but I have a question regarding how you would go about delisting one or more bases
who may be subscribed from posting to them and recreating them?
This is something I have completely overlooked since starting my own network, and I have just pondered the question, unable to come up
with an answer myself while reading your message.
One guesses that removal at the hub level will be sufficient, but I'm thinking of the good ol' days when everything was fully manual. If odd systems continue to post in those areas they'll just end up in the "bad" board.
It occurs to me, that if instead of relying on the BAD board, and instead kept the area without exporting it you could keep an eye on just what systems are posting to it with a minimum of hassle. You can then have a word with those people and see if its worth changing your mind or
persist with the removal
MeaTLoTioN wrote to Mike Dippel <=-
Thanks Mike, but I was meaning from a network hub point of view, I run
an echomail network and I was wondering how you would remove an
echomail base completely from a network so that no systems could accidentally recreate the base =)
Welp, disregard my last message. I had no idea these echos were added.
As of recent, I've only seen a handful of posts from FSX_GAMING in my
BAD area as I'm not linked to that echo, but that means I'm not linked
to any of these new ones, apparantly. I had no idea since I haven't seen
a post in any of them all year. If enough messages of interest come through in bad/unlinked area, I think about adding them. I'm linked to
the original 5 you started with. Shows how much I've been paying attention. ;)
I don't have any comment for or against any bases, but I have a question regarding how you would go about delisting one or more bases should you wish to. Is it as easy as deleting the message area from the hub(s) or
do you need to do something magical to stop people who may be subscribed from posting to them and recreating them?
This is something I have completely overlooked since starting my own network, and I have just pondered the question, unable to come up with
an answer myself while reading your message.
That's fine, this highlights the need for me to promote more often what
is currently active as an echomail post. We also have a situation where some HUBs had linked all nodes to new echos and others did not. I'd
rather the former option so that even nodes on auto can discover new traffic over time.
Then again, some hubs may not get a chance to link all echos if they direct applicants to use areafix. I guess it depends on if the applicant uses the "auto-add new areas" feature or not also. *shrug*
Sysop: | Gary Ailes |
---|---|
Location: | Pittsburgh, PA |
Users: | 103 |
Nodes: | 5 (0 / 5) |
Uptime: | 112:35:09 |
Calls: | 580 |
Files: | 2,171 |
Messages: | 61,242 |