hi there, I have a couple of feature requests perhaps for next version??

we have nodespy to watch traffic of callers, what about a nodespy
function (menu option in menus)

You already have the who is online function, and notifications sent to you when a user logs in. And you can also send them messages and user to user chat with them similar to Nodespy too. There is a snoop command too if you wish to see their session. Is there a specific feature that you think is missing from it?

Technically you could also set up Nodespy to run as a door in Linux or you could use Mystic-DOS and run it directly from that.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

what I meant to say is a nodespy for binkd traffic so can see which network is connecting, what files how many blocked connections etc (like you can with mis -server)

The version that is coming up (A44) does start to show tracked stats in the "Echonode editor" for each node as you highlight them, but it is still in its infant stages.

Currently it shows he last time they connected to you, the last time you connected to them, the number of days they've been inactive, the number of files received, the number of files (in kilobytes) received, the number of files sent, the number of files sent (in kb) and the last date the statistics were reset for that node.

This is of course something we can build upon in the future.

I haven't really thought about adding something that would show the binkp connections in real time outside of using the MIS server itself. You might be able to run MIS in non-daemon mode and then use something like "screen" to view the MIS status screen. Although I haven't investigated the different ways to do it, I do think this would be possible in Linux.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

I haven't really thought about adding something that would show the binkp connections in real time outside of using the MIS server itself. You
might be able to run MIS in non-daemon mode and then use something like "screen" to view the MIS status screen. Although I haven't investigated the different ways to do it, I do think this would be possible in Linux.

g00r00,

This is exactly how I run mine (TMUX).

Cheers,

|19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
|07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
|08:>.|15S|08ci |1577|08:|151|08/|15131|08.
|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

I haven't really thought about adding something that would show the b connections in real time outside of using the MIS server itself. You might be able to run MIS in non-daemon mode and then use something li "screen" to view the MIS status screen. Although I haven't investiga the different ways to do it, I do think this would be possible in Lin

g00r00,

This is exactly how I run mine (TMUX).

I am glad to hear someone is actually doing this, because this has sort of been my line of thinking lately. I think I may add all of the Nodespy stuff into the MIS status screen (among other new ideas/things) at some point.

Does it work well for you this way?

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

I am glad to hear someone is actually doing this, because this has sort
of been my line of thinking lately. I think I may add all of the
Nodespy stuff into the MIS status screen (among other new ideas/things)
at some point.

Does it work well for you this way?

Yes, except that it's still dependent upon the 80x25 window. Since it's not running as a Telnet session, it could be more flexible for terminal size. But otherwise, I use it religiously, along with a few windows 'tail -f xxx.log'
to monitor the logs.

One suggestion would be a "mis /reload" or a live reload while running MIS. That way you can could quickly reload the events and servers while logged
into the board.

|19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
|07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
|08:>.|15S|08ci |1577|08:|151|08/|15131|08.
|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

This is exactly how I run mine (TMUX).

I am glad to hear someone is actually doing this, because this has sort
of been my line of thinking lately. I think I may add all of the
Nodespy stuff into the MIS status screen (among other new ideas/things)
at some point.

Does it work well for you this way?

I do it the exact same way and it's been working perfect.
Alternating between the MIS screen and nodespy.

Cheers!

|15 ▀ ▐ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 ▌ ▀ |11The Bottomless Abyss BBS
|03 ▀ ▌▀ |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ▄■▐ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

I haven't really thought about adding something that would show the b connections in real time outside of using the MIS server itself. You might be able to run MIS in non-daemon mode and then use something li "screen" to view the MIS status screen. Although I haven't investiga the different ways to do it, I do think this would be possible in Lin

g00r00,

This is exactly how I run mine (TMUX).

I do this, but use screen, and also have it as a systemd service.

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

I am glad to hear someone is actually doing this, because this has sort
of been my line of thinking lately. I think I may add all of the
Nodespy stuff into the MIS status screen (among other new ideas/things)
at some point.

Does it work well for you this way?

Works perfectly for me in screen.

I'm also happy to share my systemd init script if you like.

--- Mystic BBS v1.12 A44 2020/01/16 (Linux/64)
* Origin: monterey bbs (21:1/168)

Works perfectly for me in screen.

I'm also happy to share my systemd init script if you like.

Sure if you want to e-mail to mysticbbs@gmail.com or post it here that works too.

I am open to hearing any ideas you'd like to see in the MIS "WFC" screen if
you have any, maybe that is something we can touch on it A45 too.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: Sector 7 (21:1/108)

I am open to hearing any ideas you'd like to see in the MIS "WFC" screen if you have any, maybe that is something we can touch on it A45 too.

g00r00, One thing that is buggy with MIS is that when you cycle over to the EVENTS tab, it then shows a LOGS tab, but if you cycle off EVENTS that LOGS
tab goes away. Having the LOGS access in MIS would be fantastic.

|20|15┌─|16|08┤ |08De|07ad|15be|07a|08tz b|07b|15s
|08└─┘├─┐ |08:>.|07A|08rk |0710|08:|07101|08/|0714|08.
|04■ |08└|20|15─|16|08┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|04A|07n|15al|07o|08g |08:>.|12F|04sx |1221|08:|122|08/|12123|08. |15.|04p|07HENOM|15. |08:>.|15S|07ci |1577|08:|151|08/|15131|08. |04░▒░|08▒██▄▌|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: deadbeatz.org (21:2/123)