11–20 of 80 posts
I actually was the sole developer who wrote all the software that “networked” the custom hardware together. This project was so ahead of its time and yet required some rather arcane programming knowledge. So much fun though. AMA!
I actually was the sole developer who wrote all the software that “networked” the custom hardware together. This project was so ahead of its time and yet required some rather arcane programming knowledge. So much fun though. AMA!
Can you give some details on the hardware? What was the image capture device?
No ?, just a really neat concept
I actually was the sole developer who wrote all the software that “networked” the custom hardware together. This project was so ahead of its time and yet required some rather arcane programming knowledge. So much fun though. AMA!
You mentioned that the project required some rather arcane programming knowledge. Could you elaborate on this? What areas of programming did you have to delve into that might be considered out of the ordinary?
Was there any discussion about privacy when you were implementing it?
Were there any features or functionalities that you wanted to implement but couldn't due to technical limitations at the time?
I actually was the sole developer who wrote all the software that “networked” the custom hardware together. This project was so ahead of its time and yet required some rather arcane programming knowledge. So much fun though. AMA!
Can you give some details on the hardware? What was the image capture device?
We used black and white cameras because they were both cheaper and also had much better sensitivity to low-light conditions (this has changed somewhat — but not entirely — in 20+ years) and black and white tube TVs because they were cheap. (This part was actually really dangerous — tube TVs hold enormous charges after they’ve been switched off, enough to kill someone, and we had the guts exposed on the insides of the Cocktail Consoles. Had to be very careful). We used public telephone handsets for the audio because of their durability, and video game buttons and joysticks so you could try very hard, and generally fail, to damage them.
The TV's, cameras, and telephone audio were all connected over an analog CCTV system. The camera was video source and the handset's microphone was the audio source for a given channel. The TV could be tuned to any channel, and was thus the video output device, and the handset's speaker was tied to the same channel. Thus, if you tuned to any camera, you would see and hear whatever was going on at that console, but not the other way around, so it was rather voyeuristic. If TV A was tuned to camera B, and TV B was tuned to camera A, that established a bi-directional link, which meant you could see and converse with the other person.
The serial data from all the microcontrollers were sent over serial-to-CAT5 converters, so the entire place was wired for Ethernet, but it was plain old serial over the wire. We then had these serial cards in a Dell server on the other end, which presented as roughly 100 serial ports on the server.
This was where I had to do a lot of learning. I was a good IP programmer, but I had to reach back into the depths of the kernel and learn all about TTYs and switch() and lots of other stuff that even in 2000 was sort of forgotten. It took me forever to find any good documentation on how to handle that many serial ports in a non-blocking way.
I kept asking Leo to just put a cheap Intel box in each machine and do it all over regular Ethernet, but he (rightly) kept insisting on this low-cost, rock-solid approach. Today the calculus would undoubtedly be different — you would do everything over IP — but back then Leo had a level of foresight I still admire.