SPY n watches the caller's screen live. You see their current screen immediately, not just what changes afterwards.
As a user, can't say I like that.
Rob Swindell wrote to Mortar M. on 11/02/2026 16:28 <=-
Re: Adeptxbbs 1.20a2 announcement
By: Mortar M. to Robert Wolfe on Mon Nov 02 2026 02:24 pm
As a user, can't say I like that.
That's always been a risk with BBSes though, hasn't it? That's Big
Brother is watching... :-) --
digital man (rob)
By: Mortar M. to Robert Wolfe on Mon Nov 02 2026 02:24 pm
As a user, can't say I like that.
That's always been a risk with BBSes though, hasn't it? That's Big
Brother is watching... :-)
I just assumed that's standard in all BBSes by default. I first
ran a Proboard system in the nineties for a short time, (and
could see everything a user did) so I guess I don't really
know. Once, on a Wildcat board, a sysop broke in and started
chatting with me.
Whenever I'm on a BBS, I always just assume the sysop can see
everything I'm doing if he or she wanted.
I just assumed that's standard in all BBSes by default.
Whenever I'm on a BBS, I always just assume the sysop can see everything I'm doing if he or she wanted.
"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Don't assume malice for what stupidity can explain.
Andy Alt wrote to Rob Swindell <=-
Whenever I'm on a BBS, I always just assume the sysop can see
everything I'm doing if he or she wanted.
mark lewis wrote to Rob Swindell <=-
not to mention that practically every single BBS node had a physical
CRT monitor (or printer) attached to it from the very beginning...
Mike Powell wrote to Andy Alt on 11/03/2026 15:29 <=-
I just assumed that's standard in all BBSes by default. I first
ran a Proboard system in the nineties for a short time, (and
could see everything a user did) so I guess I don't really
know. Once, on a Wildcat board, a sysop broke in and started
chatting with me.
Whenever I'm on a BBS, I always just assume the sysop can see
everything I'm doing if he or she wanted.
In the days of DOS, that was the standard. The BBS terminal was
displayed locally, in real time. If there was a user online you could
see what they were up to. SYSOPs would sometimes initiate a chat if
they thought a user was stuck, and it was a lot easier to answer a chat request from a user.
From what I can tell, most of the current BBS offerings, for linux and windows, don't have the local terminal display. You have to set up a "nodespy" or some-such if you want to see what the user is seeing.
Whenever I'm on a BBS, I always just assume the sysop can see everything I'm doing if he or she wanted.
True that is the best course to take; treat it like a public space. Still, I'd prefer it didn't exist.
As a user, can't say I like that.
Those BBS's aren't worth using. You are
in MY HOUSE, using MY COMPUTER.
I always hated that metaphor. Do you leave your front door unlocked
with a sign that says "come on in!"?
Guess you never ran a BBS before. This is done on almost ANY BBS, and if there is any that doesn't. Those BBS's aren't worth using. You are in MY HOUSE, using MY COMPUTER. I have the right to see what the fuck you are doing. Crazy fucking people. Same ones that go, I'm not telling you my real name, you'll come hack my house. Grow up.
Have you considered taking anger management courses?
Mike Powell wrote to Kurt Weiske <=-
In the early days of being a sysop, it was neat to hear the modem
answer and then watch a caller log on. Beyond that, I never really had time to sit and watch everything they did and really don't now. ;) I
do think it is really weird that some users don't realize that it has always been the case that a sysop could be watching.
I
was basically allowing you to dial in and remote control my
computer that I had set aside for that purpose.
All the software ran on my computer, your terminal simply
allowed you to interface with it. As an owner of that machine
I believe I had a right to see what you were doing with it.
Mike Powell wrote to Rug Rat <=-
Until computers got powerful enough to handle multitasking, the BBS was probably the only thing running on that machine. Aside from a screen blanker, or a monitor that was turned off, there wasn't really much of
a way for it not to be something that could be watched, or purpose or
in passing. It was all that machine was being used for.
I made a point of turning off logs on my BBS. I didn't want to know who
was calling and when. :)
Until computers got powerful enough to handle multitasking, the BBS was probably the only thing running on that machine. Aside from a screen blanker, or a monitor that was turned off, there wasn't really much of a way for it not to be something that could be watched, or purpose or in passing. It was all that machine was being used for.
software would be innefective. Specifically the standard disclaimer that a posts, messages, and files left on the system were done solely by the user. You might as well have hung a sign on your house saying "Illegal activities taking place within.".
Rug Rat wrote to Kurt Weiske <=-
Just curious (Not going to ask you your age), but when you were
running the BBS, were you a minor?
It largely depends on the State, but a lot of the methods SysOps would
use to "protect" themselves from prosecution, especially those hosting pirated software would be innefective. Specifically the standard disclaimer that any posts, messages, and files left on the system were done solely by the user. You might as well have hung a sign on your
house saying "Illegal activities taking place within.".
While not keeping logs might sound like soemthing that would placate a paranoid user. If LE had evidence of you committing a crime, they
would just show up at your door with a warrant, seize the equipment and either have everything right in front of them, or rebuild what is
missing. I wouldn't even put it past them to keep the system running
with logging enabled and get as much additional informationa as needed.
Rug Rat wrote to Mike Powell <=-
Still visable to myself and anyone who happened to be in the room when
a caller was online (Just because I was a SysOp didn't mean I did not
have friends..).
Atreyu wrote to Rug Rat <=-
"Are you a cop or a member of law enforcement" was a real kneeslapper.
There was a lot of paranoia around honeypot BBSes back after
Operation
Sundevil - a lot of BBSes went offline out of concern. When
they came
back up, a lot of callers were wary.
IF U R A PH3D, YOU NEED TO LOG OFF NOW !!!!!11!!one!@?!!
It was a fun time when computers and being online were like a secret
society that most of the people you knew or ran into had no idea.
Someone would drop a reference to being online in a conversation and
you felt like you found a kindred spirit.
c1990, there was a sysop local to the Louisville area that ran a board where there seemed to be a lot more "female" users than others. Still cannot 100% swear to it, but I suspected early on that they were mostly
all fake users... including some of the "males" who interacted publicly with them... who were actually the sysop.
On 11/11/2026 09:40 Kurt Weiske said...
IF U R A PH3D, YOU NEED TO LOG OFF NOW !!!!!11!!one!@?!!
NO CARRIER
Rug Rat wrote to Mike Powell <=-
Still visable to myself and anyone who happened to be in the roomwhen
a caller was online (Just because I was a SysOp didn't mean I did not have friends..).
We had a couple of gettogethers where we'd have people take turns
writing a post directly on the BBS. The writing got more and more
drunken as the night (and the posts) went on.
There was a lot of paranoia around honeypot BBSes back after Operation Sundevil - a lot of BBSes went offline out of concern. When they came
back up, a lot of callers were wary.
Mike Powell wrote to Kurt Weiske <=-
There was a lot of paranoia around honeypot BBSes back after
Operation Sundevil
I had to refresh my memory on that one. I thought it might have been
the raid on Rusty and Eddie's but I see it was not. ;)
Rug Rat wrote to Kurt Weiske <=-
Well, in the days of 2400bps, nothing beat actual terminal speed..
Rug Rat wrote to Mike Powell <=-
LOL, that is what the multi line BBS meets at a pizza parlor were for, though before I had I car I could never get my parents to take me to
one, and after I had a car I had much more important places to go to..
It was a fun time when computers and being online were
like a secret
society that most of the people you knew or ran into had
no idea.
Someone would drop a reference to being online in a
conversation and
you felt like you found a kindred spirit.
Well it was certainly better than being rage baited by an
algorythm designed to make you hate life and respond furiously
that the person is a blithin idiot.. :)
Rug Rat wrote to Mike Powell <=-
We once had a gettogether at a throwback 60's diner that had telephones
at every table, you could call another table by extension. We had some phreaks at the gettogether, I wondered if anyone got outside dial tone
that night.
Robbie Whiting wrote to Kurt Weiske <=-
When I put aup another board, it was a legit board and I never really regained a connection with my ahoy mateys after that.
Rug Rat wrote to Kurt Weiske <=-
If found a couple of pay phones, and asked the Hostess if those
actually still worked, and she said she believed they did (They were behind her cart, otherwise I would have actually tried one). They were located in Tomarrow Land of all places!
Rug Rat wrote to Kurt Weiske <=-
If someone had a sense of humor, they'd keep a fax machine going at
Tomorrowland if a visitor needed one.
With the Exchange outage yesterday, most people texted people (we don't
have office phones, so most people have advertised their cell phone
numbers). I was half-expecting someone to ask if we still had fax
numbers!
If they knew you and let you in, there was a hidden menu option that loaded the "real" BBS. Very cool...
If someone had a sense of humor, they'd keep a fax machine going at Tomorrowland if a visitor needed one.
Fax machines are still kept around in medical and dental offices, because they are the cheapest way of maintaing HIPAA compliance.
Rug Rat wrote to Kurt Weiske <=-
My work still has an on premise ADDS and Exchange infrastrucure. We didn't even notice :)
I keep saying that the cloud is a BAD BAD thing, but everyone just snickers and says I need to get with the program.
Tomorrowland's been replaced by Fantasyland and Discoveryland. Maybe they could setup a Retroland; lots of possibilities there.
On Fri 13-Nov-2026 7:36a, Kurt Weiske@1:218/700.0 said to Rug Rat:
Rug Rat wrote to Kurt Weiske <=-
If someone had a sense of humor, they'd keep a fax machine going at
Tomorrowland if a visitor needed one.
Fax machines are still kept around in medical and dental offices, because they
are the cheapest way of maintaing HIPAA compliance.
With the Exchange outage yesterday, most people texted people (we don't
have office phones, so most people have advertised their cell phone
numbers). I was half-expecting someone to ask if we still had fax
numbers!
My work still has an on premise ADDS and Exchange infrastrucure. We didn't
even notice :)
I keep saying that the cloud is a BAD BAD thing, but everyone just snickers and
says I need to get with the program.
Let's see hwo the NextGen infrastructure goes with the FAA.
Robert Wolfe wrote to Rug Rat <=-
yeah, I agree. A local radio station went between being on the air and off the air for 3 hours during the microft outage a couple days ago.
That actually would not be a bad theme for EPCOT, and would go every week with it's main Planet Earth ride/exhbit since that is heavily heared to the
Claude
Created 4 files, edited a file, and 55 more steps
The node monitor is built and tested. It'll be in the next
build along with the other items still in progress.
From the server console:
NODES shows the node table: user, what they're doing, time
left, idle time, connection type and address. NODE n shows
details for one node: terminal, security level, time used and
left, current message and file areas, and the last few things
the caller did with timestamps. SPY n watches the caller's
screen live. You see their current screen immediately, not just
what changes afterwards. INTERACT n watches and lets you type
into their session. CHAT n breaks in for a sysop chat. Their
screen is put back exactly as it was when the chat ends, and
chat time isn't taken off their time. MSG n text pops a boxed
message over their screen. TIME n +10 adds time; use a minus
sign to take time away. KICK n [reason] disconnects the caller.
LOCKOUT n [reason] also locks the account. Hotkeys while
watching: F2 interact on/off, F3 chat, F4 message, F5/F6 �5
minutes, F7 redraw, F9 disconnect, F10 stop watching. F1 or
Ctrl-] opens a command bar. Calling in remotely as sysop: the
Sysop menu has a new [N]ode monitor item (menu command 951). It
gives you the same table, detail page and watch/interact/chat/message/time/kick/lock-out options, with
Ctrl-] for the command bar.
What the tests covered: the remote monitor end to end, the
console version through a pseudo-terminal, and an exact match
between the caller's screen and the sysop's view while the
caller was in the full-screen editor. File transfers aren't
mirrored (watchers would only see binary noise) and still pass.
Limitations:
Doors that are handed the caller's connection directly
(DOOR32-style) bypass the BBS, so you can't watch their screen.
Doors that run through the BBS can be watched. Existing
installs need the new Sysop-menu item added; new installs get
it automatically. Now carrying on with QWK/Blue Wave offline
mail, then QWK networking, NNTP, FTP and the WFC screen. The
WFC will get spy/chat hotkeys for the node table.
Ran 10 commands
add lightbar message base selector and reader
build in AdeptREXX scripting support and an AdeptREXX
development IDE with syntax highlighting and built in command
help.
generate an AdeptREXX scripting guide in PDF format.
generate a comprehensive sysop manual in pdf format
Updated tasks, ran a command
Adept shipped REXX scripts (.Cmd). Looking at what functions
they call so AdeptREXX can run them:
Created a file, ran 18 commands
build product announcement in postable bbs message ascii format
with feature list. generate a pdf of the same info
Ran 9 commands, updated tasks
Now the lightbar code itself: a generic list picker, the area
selector, the message list and the message viewer.
build installers when finished
Noted: x86 and x64 installers will be built once everything is
done; that's already the final step of the plan. Continuing
with the lightbar code.
Created a file, ran 4 commands
add ability to run adeptrexx scripts from within the ide for
testing.
Created 12 files, read 11 files, and 65 more steps
Progress update. Done and tested since the last note:
QWK / Blue Wave offline mail:
Download packets of new messages in tagged areas. Last-read
pointers only move once the packet is actually received. Upload
REP / .NEW reply packets. Round trips checked against
independent format parsers. New Offline Mail menu ([O] on the
Message menu). Lightbar area selector and reader for ANSI
callers: Arrow keys, PgUp/PgDn, jump by number or /name, N for
next area with new mail, Space to tag areas. A scrolling reader
with a command bar, and a message list. Callers can switch it
off in Setup ([B]), and you can disable it in AdeptX.ini.
AdeptREXX, built in. No Regina or ooRexx needed. Classic REXX,
checked line by line against Regina: identical output on the
language tests. The original Adept REXX interface from
Adprexx.Doc (AdeptPrint, AdeptGetVar with the full variable
table, AdeptInput, AdeptMenuType, AdeptMessage, AdeptSend and
so on), a RexxUtil subset, and a few AdeptX extras such as a
lightbar picker. Runs from menu types 10/11, the automatic
AtStart.Cmd / AtEnd.Cmd / Main.Cmd / Exception.Cmd scripts,
events, the console (REXX script), and the command line (AdeptX
REXX script). One of the original 1996 Adept .Cmd scripts ran
unchanged. AdeptREXX IDE (AdeptRexxIde.exe):
Syntax highlighting, line numbers, completion (Ctrl+Space),
signature hints, and F1 help on 190 commands and functions.
Syntax check (F7) that also warns about unknown routines and
missing labels. Run inside the IDE (F5): the script runs in a
real in-process BBS session, logged on as a test user you pick.
It has a built-in ANSI terminal you type into, plus breakpoints
(F9), Step Into/Over (F11/F10), Stop, and a variables view. I
exercised all of this on a virtual display. Still to do: QWK
networking, NNTP, FTP, the WFC screen, then the AdeptREXX guide
PDF, the sysop manual PDF, the announcement (BBS text and PDF),
and the 32/64-bit installers.
Created 9 files, shared 4 files, and 111 more steps
AdeptXBBS for Windows 1.20 Alpha-2 is built: both installers,
the two manuals and the announcement are finished and copied to
your computer. The installers have not been run yet, because
the build machine can't execute them.
Files on your computer (C:\dev\AdeptXBBS):
Installers: dist\AdeptXBBS-1.20a2-x64-Setup.exe and dist\AdeptXBBS-1.20a2-x86-Setup.exe. Each one includes the BBS,
the nodelist compiler, the AdeptREXX IDE with its Start-menu
shortcut, and the PDF manuals. Neither contains source code.
Manuals: in docs\, and also attached here: Sysop Manual (46
pages): installation, a full AdeptX.ini reference, areas,
groups and menus, the WFC screen and node monitor, events,
FidoNet, QWK networking, email, Usenet, FTP, AdeptREXX, moving
from OS/2 and troubleshooting. The appendices cover the command
line, menu commands, meta codes, ports and the default
AdeptX.ini. AdeptREXX Scripting Guide (46 pages): tutorial
chapters, the IDE (testing and debugging), porting OS/2
scripts, a full reference built from the IDE's help catalog,
error messages and a complete example script. Announcement: a
79-column, pure-ASCII message with CRLF line endings, ready to
post, plus a two-page PDF of the same feature list. I left the
meta-code brace character out of the ASCII copy so the BBS
won't try to expand it when you post it. Project zip:
AdeptXBBS-1.20a2.zip is the whole project folder, and I
unpacked it over your copy there. Checks before packaging:
AdeptREXX output still matches Regina on the main test program.
The second test differs only in its external-routine calls,
which Regina can't resolve. Telnet sessions for scripts, QWK,
Blue Wave, the lightbar reader and the node monitor all ran
through to their menus. The FTP test suite passed every check.
Two fixes during the build:
Installer step: build.sh was looking for Inno Setup in the
wrong folder and quietly skipped it, so I corrected the path.
Before the fix it only built the programs, not the installers.
Stray file: a 20 MB Regina test package had ended up in src\,
so I moved it out and the zip shrank to 5 MB. Your folder on
C:\ may still have a copy from an earlier delivery; it's safe
to delete. Still not verified (listed in RELEASE-NOTES):
Running on real Windows at all: the service, DOOR32 doors and
the firewall rule. Whether the installers run.
IPv6.
FTP and NNTP over TLS.
Blue Wave reply packets from real offline readers.
QWK networking against a Synchronet hub (only AdeptX-to-AdeptX
was tested). The IDE and WFC screen in their native Windows
forms; both were tested on Linux equivalents. The best next
step is to install the x64 edition on a Windows machine and run
through the manual's Getting started chapter.
Adeptxbbs sysop manual
Document�PDF
Adeptrexx scripting guide
Document�PDF
Adeptxbbs 1.20a2 announcement
Document�PDF
Adeptxbbs 1.20a2 announcement
TXT
Compacted conversation
Compacted conversation
Approaching weekly limit
Adeptxbbs 1.20a2 announcement +-------------------------------------------------------------- ---------------+ |
| | A D E P T X B B S F O R W I N D O W S
| | Version 1.20 Alpha-2
| |
| | The classic OS/2 BBS, rebuilt for 32-bit and 64-bit
Windows | |
|
+-------------------------------------------------------------- ---------------+
Lone Wolfe Software is pleased to announce AdeptXBBS for
Windows 1.20
Alpha-2, a clean-room Windows edition of AdeptXBBS, the
classic OS/2
bulletin board system.
It reads the original AdeptXBBS control files, menus, screens,
prompts and
data files, so OS/2 Adept systems can move across, and it
builds in
everything a modern BBS needs: telnet, binkp FidoNet, internet
email, QWK
and Blue Wave, QWK networking, Usenet, FTP, ZMODEM and the
AdeptREXX
scripting language with its own IDE. No add-on mailers,
tossers or front
ends are needed.
FEATURES
========
BBS and telnet
--------------
* Built-in telnet server (NAWS, terminal type, binary) and
raw socket
port; IPv4 and IPv6
* Multi-node, per-address connection limits, idle and
time-limit
enforcement
* Full AdeptXBBS menu engine: 1.09 and 1.07 menu formats,
every item
restriction
* Language.Text prompts and the complete set of AdeptXBBS
meta codes
* RIP / Avatar / ANSI / ASCII screens chosen per caller
* Doors: DOOR.SYS, DORINFO, DOOR32.SYS, socket and stdio
doors
Messages and files
------------------
* Lightbar area selector, message list and reader for ANSI
callers
* Full-screen ANSI message editor with quote window, plus
the line
editor
* New scans, quick scans, searches, tagged areas, personal
mail check
* QWK (QWKE) and Blue Wave offline mail with reply upload
* Built-in ZMODEM and ZMODEM-8K with crash recovery, YMODEM,
XMODEM
* File lists, searches, new files, batches, FILE_ID.DIZ, ZIP
viewing
Networking
----------
* binkp/1.1 mailer: CRAM-MD5, NR, ND, MB, CRYPT, GZ
compression, IPv6
* GateKeeper-compatible tosser/scanner, AreaFix, file
requests
* Nodelist compiler with NODEDIFF, CRC check and binkp host
lookup
* QWK networking as a node (FTP or folder) or as a hub for
other BBSes
* Usenet (NNTP) gateway with AUTHINFO, STARTTLS and implicit
TLS
* Internet email: SMTP, submission, POP3, TLS, smarthost or
direct MX
* FTP server for the file areas: BBS logins, resume, TLS,
IPv6
Sysop tools
-----------
* Full-screen wait-for-call console with node table, status
and live
log
* Node monitor: watch any caller live, type for them, break
in for
chat,
pop up messages, add or take time, disconnect or lock out
* Remote node monitor from the Sysop menu while logged on
* Event scheduler, Windows service, command-line user and
maintenance
tools
AdeptREXX
---------
* Built-in REXX interpreter - no Regina or ooRexx needed
* The original AdeptXBBS REXX interface; OS/2 scripts run
unchanged
* AtStart.Cmd, AtEnd.Cmd, Main.Cmd, Exception.Cmd, events,
console
* AdeptREXX IDE: highlighting, completion, F1 help, syntax
check,
and test runs in a real BBS session with breakpoints and
stepping
Packaging
---------
* Separate 32-bit (x86) and 64-bit (x64) Inno Setup
installers
* Sysop Manual and AdeptREXX Scripting Guide in PDF
* Runs on Windows 10 (1903+), Windows 11 and Server 2016+
(.NET 4.8)
STATUS
======
This is an alpha release. Most functions were tested end to
end in the build
environment; running on real Windows, IPv6, Windows services,
DOOR32 doors
and the installers themselves still need testers. Please
report what you
find - the release notes list exactly what has and has not
been verified.
AVAILABILITY
============
Download AdeptXBBS for Windows from the support BBS. Feedback,
bug reports
and questions are welcome there.
Program Written by Robert Wolfe <rwolfe@twc.com>
Support BBS - <http://brinkbbs.org>
(C)opyright 2026 by Robert Wolfe & Lone Wolfe Software.
Claude finished the response
--- Sabre/Win64 1.0
* Origin: Lone Wolfe Software - the Homew of SabrePoint (1:261/20.716@fidonet)
Robert, Your BbS came on my phone screen while I was reading this post.
I suppose I touched a part of the screen to cause the Log On so I backed out of
that screen to see the rest of your post (and reply).
It surprised me a lot as I never had this happen in the 3 years I've been using it .
Your BBS Log will show what happened.
| Sysop: | KrAAB |
|---|---|
| Location: | Donna, TX |
| Users: | 4 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 170:04:29 |
| Calls: | 57,180 |
| Files: | 3,971 |
| D/L today: |
25 files (9,999K bytes) |
| Messages: | 61,523 |