Subj : Synology Docker Mystic Test
To   : opicron
From : Accession
Date : Thu Feb 13 2025 06:06 pm

Hey opicron!

On Thu, Feb 13 2025 10:02:58 -0600, you wrote:

 > Your solution wasnt feasible, because using that way Mystic is already unresponsive
 > and doesnt drop the user. Actually we cant even connect to any node. And its not
 > because the nodes are busy, its because Mystic become unresponsive, completely.

I understand that now, of course. However, it was still just another option to the script that was posted. Nothing more, nothing less.

I'm glad you at least gave it a try (even though it didn't work).

 > Again, it might have to do with server too-- or maybe the two together. Anyway
 > that was the issue.

I'm pretty confident in saying Mystic was probably never tested (by the author) in a docker instance. At least he never mentioned it to me, ever.

 > With manual drops, in whichever way works out better for me.

 > I think no software is 100%, our creativity and workarounds are making our
 > lives, and indirectly the software better.

I agree completely. Most definitely go with whatever works best for you. The less headaches you run into the more time you have enjoying it, rather than fixing it. However, I would still always recommend running _any_ server (BBS or not) that doesn't have built-in firewalling/filtering be run behind a perimeter firewall/filter, though.

Looks like you now have something in place to help with that, now. ;)

Regards,
Nick

.... He who laughs last, thinks slowest.
--- slrn/pre1.0.4-9 (Linux)
 * Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

.