Subj : Synology Docker Mystic Test
To   : fusion
From : Accession
Date : Tue Feb 11 2025 07:18 pm

Hey fusion!

On Wed, Feb 12 2025 00:43:42 -0600, you wrote:

 >> Pretty sure if you force ANSI instead of using detection, it does
 >> basically the same thing as your MPL script does without any
 >> "workarounds."

 > the "workarounds" here were referring to MIS getting into a state it
 > won't accept connections, requiring his script to restart the docker
 > image.

I'm fairly certain this is what I replied to:

[ snip ]

 op> I had a look, thank you for the lead! Not sure how I would get this
 op> to work. However, you did give me an idea. If I check TERMTYPE in
 op> Mystic connect.mps I can kick the connection if termtype is ASCII.
 op> Which is the usual one for the bots it seems.

 > yeah that's what i currently do. just dump a message "this bbs
 > requires an ansi capable terminal," list off a few of them and
 > hangup. on a47 though..

<script was posted doing exactly what I wrote Mystic could do without a script>
<workarounds were mentioned>

[ snip ]

 > somewhere between the bot being allowed to connect, dumping whatever
 > it does at the mystic login prompt, and then getting booted for
 > incorrect passwords or idle timeout, is causing MIS or mystic to mark
 > the node BUSY permanently, among other issues.

What I wrote in my reply was a possible configuration option (as in something the BBS offers, rather than using a "workaround"), which doesn't go as far as the login prompt or passwords and idle timeouts. This happens as soon as you connect, the software version and copyright is displayed and then it displays the "Detecting Emulation" prompt (which this prompt can also be changed to do whatever you want it to do).

 > that's the only problem. it doesn't really matter whether or how we
 > boot the user for not having ANSI. what if i want to allow non-ANSI
 > users? sync does.. mystic does too, but the bots are breaking the
 > server.. it's a bug ;)

If you wanted to allow non-ansi callers, then you wouldn't have wrote that script you pasted, which is what I was replying to, now would you?

So you're basically saying that because Mystic doesn't have pfsense features/functionality built into it, it's buggy? I can't imagine why g00r00 disappears from the scene for years at a crack. lol

I'd imagine that's probably your (or their) solution, though. Use pfsense or something similar to filter telnet (or whatever ports you have open) before Mystic loads to take care of bots that may connect multiple times from the same IP address at the same time that could possibly hang the software.

This is probably what you (or anyone) would do with any other BBS software besides Synchronet, right?

Synchronet may have these features built in, but how many other BBS softwares have that?

That said, you should probably take matters into your own hands, rather than waiting for James to come back (and who knows, it may never happen again). It's not like he's getting any kind of paycheck for Mystic or anything. So there's really no incentive for him to come back besides maybe his own boredom, and the sudden urge to listen to people complain about the software he created. lol

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)

.