2 ms·
RISKS has a more complete description and explanation, from Hubbard himself: Failing to find anything that might suggest that rwall would do anything nasty bey
by dredmorbius 6y ago
RISKS has a more complete description and explanation, from Hubbard himself:
Failing to find anything that might suggest that rwall would do anything nasty beyond the bounds of the current domain (or at least up to the IMP), I tried it. I knew that rwall takes awhile to do its stuff, so I left it running and went back to my office. I assumed that anyone who got my message would let me know.. Boy, was I right about that! After the first few mail messages arrived from Purdue and Utexas, I begin to understand what was really going on and killed the rwall. I mean, how often do you expect to run something on your machine and have people from Wisconsin start getting the results of it on their screens?
http://catless.ncl.ac.uk/Risks/4.73.html#subj10.1 http://catless.ncl.ac.uk/Risks/4.73.html#subj10.1
- pyuser583 6y agoI found that via Wikipedia. The other articles are fascinating. One was about privacy. It seems many of those risks have never really been solved - air traffic control failure being the exception.
- dredmorbius 6y agoThe RISKS digests are an invaluable resource, though I'd argue moreso for the earlier period, through the mid-to-late 1990s.