Warpslide wrote to esc <=-
I thought part of being a sysop was being sadomasochistic enjoying the pain and suffering of trying to get everything to work. At least
that's how it was for me trying to get Telegard talking to FastEcho, AllFix & FrontDoor back in the day.
Thats the thing, I haven't found anything. I've found how to set
yourself up to an existing network, but not how you make a new one.
Then again, if that was common knowledge, we'd have everyone making
their own 'nets and abandoning them.
Thats the thing, I haven't found anything. I've found how to set yourself up to an existing network, but not how you make a new one.
Then again, if that was common knowledge, we'd have everyone making their own 'nets and abandoning them.
I don't think there is much point in creating a net today, aside fromQWK based networks seem more doable.
the exercise.
I don't think there is much point in creating a net today, aside from
the exercise.
QWK based networks seem more doable.
Oh, but when it all works -- glorious!
Then, it's time to switch platforms. :)
Back from another burnout phase that was induced by Mystic problems on
the FTN hub. which have since been fixed. Toom me another several weeks to get myself ready to partake in the BBSs again. :)
I've also been sidetracked by some major ham radio projects, but along
the way I have gained a lot of Docker knowledge. :)
ay think, because I *can* feel my energy and enthusiasm rising day by
day when it comes to BBSing. And I know what it's like to lose interest when things get overwhelming, whether it's BBS related... or
life-related. Ugh.
First up: a new board I'm hand-crafting around all thing 'retro' using retro systems. Well, older things anyway. A DOS-based BBS (Renegade!). It's been fun getting all the parts to work w/DOS -- telnet server, mailer, tosser, events, etc.
Also, I have a small, niche FTN I've been protoyping since last year.
And of course gOLD mINE still needs love.
Anyway, welcome back ya'll and see you around the bbsverse!
FTN is more widely supported but can be a lot of work for the hubs to
keep the nodelist up to date and weed out nodes that just vanish and
also adding new node who want in.
These words ring true to me... it's a mix of nodes that vanish or nodes that have issues and the HUB can't connect to them (IP block in place etc. etc.) that can be a PITA from my POV :)
Oh and hi Al :)
Long time no chat... hope you're well and not too hot in Canada right now.
I don't think there is much point in creating a net today, aside from the exercise.QWK based networks seem more doable.
On 07-29-22 14:54, Avon wrote to Vk3jed <=-
On 26 Jul 2022 at 08:05p, Vk3jed pondered and said...
Back from another burnout phase that was induced by Mystic problems on
the FTN hub. which have since been fixed. Toom me another several weeks to get myself ready to partake in the BBSs again. :)
I've also been sidetracked by some major ham radio projects, but along
the way I have gained a lot of Docker knowledge. :)
welcome back Tony, I know this feeling also.
Been busy support parents with illnesses so a bit time poor but dipping in/out of BBS when time permits and keeping my time on BBS fun for me.
Glad you got some docker time. I confess I was quite taken with it when
I played with it. I feel like I need to start over with a new HDD for
all my linux stuff as bits were not working as I wanted and permissions kept foxing me... but for now I am leaving it all well alone :) less stress :)
On 07-28-22 13:27, Al wrote to Utopian Galt <=-
QWK networks are easier for the network admin. Nodes poll when they
choose and come and go as they please. There is nothing for the network admin to do once setup but to make sure his node/hub is connectable.
FTN is more widely supported but can be a lot of work for the hubs to
keep the nodelist up to date and weed out nodes that just vanish and
also adding new node who want in.
ay think, because I *can* feel my energy and enthusiasm rising day by
day when it comes to BBSing. And I know what it's like to lose
interest when
things get overwhelming, whether it's BBS related... or life-related.
Interesting. Perhaps I should give this a shot. So in other words, the
BBS that's actually listening and calling out for mail, occupying port
24554 or whatever it is, is a "shadow" instance that actually
communicates with the real BBSes behind the scenes. Is that a correct understanding?
That's correct! The hub/boss BBS uses your main node credentials to slurp up the network(s), and then you'd have additional Echomail Nodes for each of your downlinks, e.g. for my point: 21/4:158.1 for BBS 1, 21:4/158.2
for BBS 2, etc. Then you'd just add those nodes to the "Export To..." fields for each echo area in the Message Base Area.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 95 |
Nodes: | 16 (0 / 16) |
Uptime: | 02:08:37 |
Calls: | 3,568 |
Calls today: | 4 |
Files: | 8,461 |
Messages: | 338,770 |
Posted today: | 1 |