Hello G00r00,

thanks for the hard work You're providing to the community.

I dare to ask You whether it would be possible to set timeout for
systop to something different than ordinary user. I like to connect
and hang with my sysop account for whole day or so.@But the users...
You know they like to close the browsers etc.

So would that be possible to set different timeout for my sysop account
and that would be other than system-wide. It's just an idea. I can live
without it.

Also I was thinking about asking You regarding the support. I dare to propose that according to experiences would You prepare something like automatic mail that will be sent in case You wouldn't log for e.g. a year or so with the source codes of Mystic? I know that's very sensitive topic. But as You can see once the head programmer of a door, program or etc. would disappear from the digital life the product will remain unsupported and unchangeable. I do not
ask You to release the source codes to public right now. Possibly You want to monetize it. Or would like to have total control over the stability of Mystic BBS. But I propose to You to consider preparing mechanism that would release the source code once You would Your work is done.

Thanks for everything and I'm huge fan of Your work

Best regards

Shinobi
.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: INFOLINKA BBS (21:1/153)

I dare to ask You whether it would be possible to set timeout for
systop to something different than ordinary user. I like to connect
and hang with my sysop account for whole day or so.@But the users...
You know they like to close the browsers etc.

So would that be possible to set different timeout for my sysop account and that would be other than system-wide. It's just an idea. I can live without it.

Go into the user editor, find your account, and turn on "No Timeout" in the flags section. You should be good to go after that!

--- Mystic BBS v1.12 A39 2018/03/26 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)