TW> One more thing I tried was to chown nodespy* to root then run it.  This
 TW> got rid of the "unable to establish a snoop session" error; it shows the
 TW> action bar at the bottom, but a blank black screen (the ascii/ansi
 TW> screens do not display), and on the client 
 TW> end, the smoothness is gone.  The screens display delayed in chunks of
 TW> data instead of a smooth stream.

It certainly seems like you have permissions issues causing these problems.

What I would do is chown everything back to your BBS user and start from there.  There is no need to ever set anything to root or use root.  When your BBS is completely shutdown run "sudo ./mis killbusy

When you do set root ownership or run as root user, any files it touches is going to now be owned by root.  This is going to break things across the board.

I can't comment on it slowing down but I will do some testing here to see if I can reproduce it and clean it up.  When you snoop it is doing more by sending data to more places, so it will require more processing power while snooping.  But I wouldn't think it'd be all that noticable to a remote user.  What are you running it on?  Maybe if its a Pi 1 or Zero or something it but outside that I wouldn't think there would be a dramatic performance hit.  I'll check into it!

I will also change NodeSpy to change the root user like the rest of things do, so that you'll be able to run it as "sudo ./nodespy" without causing any issues in the future.

... The seminar on time travel will be held two weeks ago

--- Mystic BBS v1.12 A49 2023/01/17 (Windows/64)