TID: Mystic BBS 1.12 A45   
   MSGID: 1:227/702 0c9c3ce2   
   REPLY: 2:221/360.0 5f19632e   
   TZUTC: -0400   
    AA> I don't know what nodespy is, and the description at github sounds greek   
    AA> to me (middleware within middleware, node.js, etc..)   
    AA>    
      
   Nodespy is kind of like the old waiting for caller screens that would allow   
   SySops to view basic BBS stats such as callers, emails, posts, for the day,   
   without having to login to see if we have email.  In the dial up days waiting   
   for call screens allowed us sysops to auto set security levels for users,   
   hang up on them if they were malicious, jump in chat if paged, etc... nodespy   
   is similar in that we can pick a node someone is connected to and perform   
   basic functions like that.  I had been using it to see if I had any email or   
   calls, so I didn't have to go through the BBS login process to find out.    
   However, when a user would connect, for some reason my Mystic nodespy take a   
   minute to auto launch a separate terminal and display the user logging in. That   
   delay was causing the issue.  So I just quit launching the application and   
   the problem went away.  I still have a short cut to the ap so I can view the   
   stats, then close it right back out.  However another sysop tested his the   
   same way and was unable to replicate the problem.  So .. I'll likely upgrade   
   my .45 to .46 Mystic this week to fix the problemo.   
      
   -Doug   
      
   --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)   
    * Origin: The Underground [@] theunderground.us:10023 <-port (1:227/702)   
   SEEN-BY: 1/123 90/1 120/340 601 123/131 226/30 227/114 702 229/101   
   SEEN-BY: 229/424 426 452 664 1014 240/5832 249/206 317 400 292/854   
   SEEN-BY: 317/3 322/757 342/200 633/280   
   PATH: 227/702 229/426