You're going to do what you want anyway, but I thought you should know Temple OS with networking is a bad idea. TAD never did proper multitasking with process multiplexing, he ran everything with cpu0 and then would move things into background by putting them on one of the other CPU's cores (cpu1..cpuX). If you have network stuff running and you get a bad request, cup0 wont be able to switch the process to background and you will freeze the system. It would work like the Slowloris Attach. Slowloris might also work on Temple OS as a client because even the GUI for Temple was complied to HolyC and then ran; if it didn't compile you couldn't run it. Temple OS never had a proper interpreter probably down to the same reason. If you were to create a dad message that your Gopher client has to read, you can't kill it and get back control because the controlling cpu0 is also processing bad message and has already locked-up from the bad request. Since you have to pass all commands though the controlling cup0 and cpu0 is the one that the process runs it, when it comes time to kill the process early the thing that takes the command is busy with the bad process. (And wont recover until the process cedes control back to the user.) On real operating systems, that people actually use, there is this idea of process multiplexing where the kernel uses a model of processes in a structured hierarchy to decide which work gets done next. TAD never created any of that because he was perfectly happy to have the system crash.
The decisions that made Temple easy to implement would by modern standards make it extremely insecure and unreliable. TAD made Temple run entirely in Ring0 which is fast, let's you play directly with hardware, and is a nice toy, but means that if you can get a malicious program running on the a Temple system that program would has access to everything. There would be no file permissions, user accounts, certain files that the operating systems does not allow to be overwritten, nothing like that; everything is fair game. This was never a problem for TAD in his own immortal words, "[Temple OS] never runs code I didn't write." All of this mattered very little at the time because after the first physical computer TAD got working with Temple stopped working TAD exclusively ran Temple in Virtual Box, even describing this in Temple OS' promotional material.
TAD was a man out of time. He created an operating system that had no commercial value the way he intended it to be used. Maybe it Temple had come out in the 1970s people might have used it on their home computers. TAD was a mad genius who never considered the value of what he had actually created. At first TAD wanted to sell Losethose (temple predecessor) as a commercial operating system, but never realized how it would compare as a market offering to it's competitors. Arguably all the things that are design flaws in Temple would have made it a good educational tool. Students could use the system to learn about how to implement core OS parts and how these systems work. Being a simpler system, it might have been a good choice in a scholastic setting for students to cut their teeth on. TAD never considered this. He just got crazier and crazier until he died.
