Thematically the school administration putting in what seemed like arbitrary rules just inspired us to work even harder to get access.
HISD also locked down "author" mode which was required to write new programs (called lessons) in PLATO's programming language named tutor.
Someone eventually cracked the account owners password, which is how some people ended up with accounts with author rights. We ended up replacing the login program on HSEP's PDP 11/34 so we always had super user privileges and I managed to socially engineer privileged access to our CDC mainframe. My flashhook dialing buddy figured out the system operators had buried end of file characters in the system docs on the CDC mainframe and we were able to find lots of interesting new commands to run after that. Again, telling us we couldn't do something just inspired us more. OK, upon reflection we were just hacking anything we could get our hands on.
Frankly I couldn't tell you exactly how I socially engineered it any more but I managed to track down an oil company here in town that not only had a PLATO terminal but a printer and gained access to both over the summer. Needless to say this was an amazing coup for a high school kid who just wanted to do a little coding and play a few games, if I say so myself.
I no longer have the long rolls of yellow paper from playing TREK and other games on an ASR 33 connected to the CDC mainframe or indeed anything else from high school, but the PLATO dot matrix screen print of Labyrinth's start screen remains a treasured possession to this day.
Like realtime chat with any other user, character by character updates (what, you have to press enter to send? primitive!)
Friday afternoon dogfights used a lot of resources, but were super cool. Tens and maybe 100 users all in the same real time flight space, duking it out...
Is that really good UX? I want to have a chance to fix my typos and other errors before sending.
A shared system that could survive being interrupted whenever any of its users pressed a key still was relatively rare.
So I guess this might ¿partly? Have been to show of the capabilities of the system. At 1200 or maybe even 300 baud, it may also be the better UX, but I wouldn’t know.
Empire was built around a 10 second replot mechanic and you frequently used the STOP button to stop the screen from drawing so you could get interactivity back quickly.
Realtime chat was amazing, especially with the ability to move characters around/erase characters with the pixel addressable 512x512 plasma screens; people would draw art by using characters, then moving the cursor back over them, and then erasing, or drawing in another character. O shift-space * shift-space ? would be O, * and ? on top of each other, which kind of looked like a smiley face. Fun times.
This one was standalone, so a later model. Also the screen was bluish-white as opposed to the orange ones that I see photos of. All of the software was on floppies and much of it of the educational/industrial ilk. How to Not Kill Yourself With Chemicals, and So, You're a Sociopath. That sort of thing.
It was awesome.
IBM had big flat panel plasma displays in the early 1980s.[1] Early in the history of AutoCAD, a driver was written for one of those things interfaced to a PC. The slow update rate was a big problem for the cursor. Orange plasma displays struggled along for decades, but the slow refresh rate limited their usefulness.
I was fortunate to have a parent who worked for Dr. Bitzer and we had a PLATO terminal at home, hardwired in to the university mainframe at 1200 Bd. Played most of the games mentioned in the article along with Empire, a Star Trek-inspired multiplayer team game. Great memories.