Then will circle back to echomail areas and look to consolidate some down also.
Will be pruning several inactive nodes in the coming day or so...
Will be pruning several inactive nodes in the coming day or so...
Hey Avon, I'm curious, how do you figure out who is active and who is inactive? I really just want to learn more about FTN in general hehe.
On Saturday, September 17th Avon was heard saying...
Then will circle back to echomail areas and look to consolidate some also.
Any idea on what this will look like yet?
Folks seem keen to join and while they are active it's all milk and cookies but when they decide to shutter their BBS or not take part in fsxNet it's super rare for them to contact me or another HUB admin to say they are shutting down. Those who do are certainly appreciated for taking the time to let us know ;)
I've noticed BBSers generally don't often notify people when they're
going down for other things too. There's a message network I'm
connected to now, but over the years it has gone down and changed hands several times without me knowing because I didn't see a notification
about it. :)
Avon wrote to NuSkooler <=-
Then will circle back to echomail areas and look to consolidate some also.
Any idea on what this will look like yet?
Not totally but I'm thinking merge a number of topics down to far
less echos. There's about 8 echos off the top of my head that
could go this way or just be pulled.
I think it's been good to try some things but merging some would
be the way to go I think.
For likes of Enigma 1/2 and Talisman (and Mystic) it's been
suggested to merge them down to the FSX_BBS echo but I am not
sure about that. Still kind of like the separated support making
it easier to find subject related stuff...
Any thoughts appreciated on what should stay/go/merge etc.
I look at some of the stats reports in the echomail stats echo, if files and messages are getting up to 60+ days or more then those are nodes
that get pruned.
Not totally but I'm thinking merge a number of topics down to far less echos. There's about 8 echos off the top of my head that could go this
way or just be pulled.
Not totally but I'm thinking merge a number of topics down to far less
echos. There's about 8 echos off the top of my head that could go this
way or just be pulled.
Why?
Also, keep in mind, that pruning echos means everyone has to update their systems (even if it's just setting those areas as readonly or archived) though adding echos is much easier, because you can ignore them and link them when you like.+1
As for getting rid of Talisman / Enigma echos, or rolling them into
general BBS support - I'm not a fan of that,
because I don't want to wade
through a bunch of other bbs support questions, and then miss one and
have people think I don't care.
I look at some of the stats reports in the echomail stats echo, if files and messages are getting up to 60+ days or more then those are nodes that get pruned.
I think it's been good to try some things but merging some would
be the way to go I think.
I would think Mystic could/should have it's own echo due to the number
of people using it, and larger message volume. The other BBS software
has far fewer users and could be combined into one echo.
Additionally, I think the Sports/Gardening/Artistic/Transportation (and probably a few more, those are from memory) don't
get enough traffic to justify having an echo. Having fewer echos with more messages in each
seems to be a better approach to me. Cheers!
and messages are getting up to 60+ days or more then those are nodes
that get pruned.
I think it's been good to try some things but merging some would
be the way to go I think.
I agree with that idea 100%.
I would think Mystic could/should have it's own echo due to the number
of people using it, and larger message volume. The other BBS software has far fewer users and could be combined into one echo.
Additionally, I think the Sports/Gardening/Artistic/Transportation (and probably a few more, those are from memory) don't get enough traffic to justify having an echo. Having fewer echos with more messages in each seems to be a better approach to me. Cheers!
Ah gotcha. I'd love to figure out how to build my own local stats to understand messages from each echo, each network, last update, etc., but maybe this is something I'll have to figure out on my own if using
Mystic for my binkp server.
As for getting rid of Talisman / Enigma echos, or rolling them into general BBS support - I'm not a fan of that, because I don't want to wade through a bunch of other bbs support questions, and then miss one and
have people think I don't care. Plus Bryan and I are here. It also seems to me, that they are obvious echos for people to not link to - someone running Renegade might not care what happens in Talisman echo.
When fsxnet started, it had one echo, fsx_gen (I'm sure you remember, but others might not) and there was an issue where new people often thought fsxnet was technical related and non technical posts weren't welcome.
By having a gardening echo, people can be sure gardening chat is welcome, and while most of the time they might be out in the sunshine not posting messages, it's there if they want to. If gardening was relegated to general, it may lead to people thinking well gardening chat isn't really wanted - even though general covers it.
Also, keep in mind, that pruning echos means everyone has to update their systems (even if it's just setting those areas as readonly or archived) though adding echos is much easier, because you can ignore them and link them when you like.
What about having some notice in the info packet instead, like General (High Traffic) Gardening (Low Traffic)
Cryptography (Very Low Traffic)
If people don't want to see echos with few messages, they can unlink from them.
Why?
Will be pruning several inactive nodes in the coming day or so...
Then will circle back to echomail areas and look to consolidate some
down also.
I run the same sort of stats here, but on the mailbox/staging
directories for each downlink.
I think these ones are generated using scripts that shipped with HPT tosser etc...
Also, keep in mind, that pruning echos means everyone has to update
their systems (even if it's just setting those areas as readonly or archived) though adding echos is much easier, because you can ignore
them and link them when you like.
What about having some notice in the info packet instead, like General (High Traffic) Gardening (Low Traffic)
Cryptography (Very Low Traffic)
People can then decide and prune themselves.
As for getting rid of Talisman / Enigma echos, or rolling them into general BBS support - I'm not a fan of that, because I don't want to
wade through a bunch of other bbs support questions, and then miss one
and have people think I don't care. Plus Bryan and I are here. It also seems to me, that they are obvious echos for people to not link to - someone running Renegade might not care what happens in Talisman echo.
I agree. Unless either you or Bryan are keen to see those echos removed I'm more than happy for them to remain. I appreciate that you guys both post and support them with updates and offering help to folks who are using the software you both write.
I'm also of the same view to retain the Mystic echo despite g00r00 not being active in it.
Re your Gardening comments, not I'm not thinking of moving such a topic back to FSX_GEN but am thinking of grouping several topics that currently have some chatter in specific echos down into one more broader encompassing echo.
My thinking is that echos such as DIY, arts, gardening, transport, food, could merge into a lifestyle echomail area that also covered travel, health and fitness, pets, road trips, travel for example.
As far as the fsxnet echos I am happy the way they are and I agree
with adam, if members don't want same echos. them unlink them
but I except what ever happens
What do we need to do on our end once you prune these? Do I need to manually remove the old bases? Do I need create new ones? Just want to know what all is involved.
Yes please! Also yes, Mystic gets so much traffic I think it clearly
makes sense with or without it's author.
Re your Gardening comments, not I'm not thinking of moving such a top back to FSX_GEN but am thinking of grouping several topics that curre have some chatter in specific echos down into one more broader encompassing echo.
This makes sense to me
My thinking is that echos such as DIY, arts, gardening, transport, fo could merge into a lifestyle echomail area that also covered travel, health and fitness, pets, road trips, travel for example.
+1 to this general theme.
Thanks Avon!
If we do end up pruning some echomail areas and merging things down to a few new ones I will ensure the old messages are copied across to the new echomail areas.
On 19 Sep 2022 at 07:57a, claw pondered and said...
Hi there.
You would want to delete the old message bases from your BBS and ensure you are delinked from them at your HUB (assuming your HUB admin has not already done this for you).
If we do end up pruning some echomail areas and merging things down to a few new ones I will ensure the old messages are copied across to the new echomail areas.
You can then either manually add any newly established echomail areas to your BBS (assuming we set up a few new ones) or set your BBS to auto-create them when messages are sent to them and to your BBS from
your HUB.
Once the HUB has made any changes to available echomail areas you may
want to do an areafix to list and confirm you are linked to them.
I would then send a Areafix request to the HUB to request a rescan of the contents of the new echomail areas so that the HUB sends your BBS all the messages it has on hand for the new bases you're after.
Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz
--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
So the next question. When is it ready for me to do all this?
On 09-20-22 19:25, Avon wrote to claw <=-
On 19 Sep 2022 at 07:57a, claw pondered and said...
What do we need to do on our end once you prune these? Do I need to manually remove the old bases? Do I need create new ones? Just want to know what all is involved.
Hi there.
You would want to delete the old message bases from your BBS and ensure you are delinked from them at your HUB (assuming your HUB admin has not already done this for you).
If we do end up pruning some echomail areas and merging things down to
a few new ones I will ensure the old messages are copied across to the
new echomail areas.
Not something I really want to go through, especially before the end of this year, where I'm in a high stress period with some downtime expected for a house move. I need a lot of "spoons" to get through that process.
If we do end up pruning some echomail areas and merging things down to few new ones I will ensure the old messages are copied across to the n echomail areas.
How would that work, technically?
On 20 Sep 2022 at 09:19a, Oli pondered and said...
If we do end up pruning some echomail areas and merging things
down to few new ones I will ensure the old messages are copied
across to the n echomail areas.
How would that work, technically?
read/write permissions I expect.
My question was more about the copying and distribution of the old
mails. Do you want to copy the messages as they are to the new echo and then export the old mail from the new echo to every downlink? Will
MSGIDs and dates stay the same? I would expect some tossers / nodes
would sort the mails to the DUPES or BAD area. Or do you want to forward the messages with a new header to the new echo, which would break threading. Or is there some magic tool or other way of merging echos
that would avoid the problems? I'm curious if merging of old messages
into a new echo is possible without creating a mess.
Anyway, I don't grant permissions to copy/merge _my_ mails from old to
new echos. Quoting and cross-quoting is fine, but I expect that my original mail is distributed unmodified, which includes the AREA: line
and the context they are appearing in.
My proposal: create new echos (if you really have to) and retire the old ones slowly. First read/write with weekly reminders, then read-only.
When everyone had a chance to pickup the new echos, then the old ones
can be purged from the Hubs / Areafix. BBSing is slow.
On 09-22-22 12:20, Avon wrote to Vk3jed <=-
my apologies then (in advance) should we end up changing, but I think
it's reasonable to make changes from time to time and those changes can include removals as well as additions.
I guess best case for you may be to simply set removed bases to sysop
only on your system so no one can post to them and allow your system to auto create anything new sent to it, of which there may only be a very small few.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,042 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 01:33:55 |
| Calls: | 500,919 |
| Calls today: | 6 |
| Files: | 109,372 |
| D/L today: |
16,756 files (2,536M bytes) |
| Messages: | 305,076 |
| Posted today: | 7 |