'A fluke': The oldest webcam is still watching over San Francisco
sfgate.com
sfgate.com
Maybe it's just me but I couldn't find the direct link in the article except in one caption field and a few invisible credit fields.
You can replace each of the pieces slowly over time, but in the viewer's eye it is still the same.
I attribute the slightly salacious site title to either irony or a less-than-perfectly-idiomatic command of English, since all the linked sites were completely innocent scenes like this.
I spent a lot of time looking at pictures from around the world. Needless to say, I miss that internet a lot.
> held up by a couple of pieces of blue gaffer tape.
Gaffer tape is fairly expensive, more expensive than Gorilla tape of the same width and length. At times, gaffer tape is worth its volume in dimes. That isn't a cheap fix nor is it a good fix. Gaffer tape has a purpose and that isn't it (unless for some reason it needed to be disassembled often). Duct tape would have been a better fix and probably cost a sixth as much, but would have been permanent unless leaving adhesive all over it doesn't count as totaled.
edit: I think you're absolutely right.
fun fact: at the current time afaik you can get the whole rainbow of colors of masking tape in NYC, but LA seems to only have blue and neutral/tan
> We've slightly changed campus locations a few times as necessary over the years, to prevent being shut down by the university.
Gaffer tape doesn't leave residue (or very little that's easy to remove), so I can imagine "not damaging the building" (making marks on the glass) being a condition of it staying up.
In the student lab I hung out in, there was a Mac IIcsomething and somehow it got a video capture card and a video camera. The video capture app was left running on the system (in the startup items too) and would capture once every so often (lets say about a minute). But, by itself, this wasn't enough. So it also ran an ftp server. We then had another system with a cron job and ftp the file to the unix system hosting the web server.
Looking it up...
https://web.archive.org/web/19990221185541/http://upl.cs.wis...
something similar happens when the oldest living human dies... if they were exceptionally long lived, there's a good chance the next in line is not, so it can be a big jump down in age
https://sites.google.com/a/montulli.org/about-fishcam/Home/h...
The reporter seems entirely too young to know how to capture how archaic the thing really was.
Contradiction? Maybe they meant that the first internet cam predated the web?
Edit: https://en.wikipedia.org/wiki/Trojan_Room_coffee_pot has more details. So the Trojan Room coffee pot cam began its life as a local network cam which then went on to become the first web cam. So no contradiction there! Interesting bit of history!
I do something similar and run nginx in a docker container, so all I need to do is 1) run a docker container and 2) run ffmpeg elsewhere to send an input stream to the docker container. There are tutorials all over the web for doing this. Try searching for "ffmpeg nginx rtmp hls docker" without quotes.
There should be a way to get it working from a browser, but it serves as a possible inspiration that runs well without having to install the kitchen sink to get it working.
The DEVICE_NUMBER may need to be changed (e.g, 0, 1, 2, 3, 4, etc.)
#!/bin/bash
# to view the stream, open with VLC: http://your-ip:8088/
if [ "$1" != ""]; then DEVICE_NUMBER=$1 else DEVICE_NUMBER=4 fi
cvlc -vvv v4l2:///dev/video$DEVICE_NUMBER --sout '#transcode{vcodec=mjpg,acodec=none}:std{access=http,mux=mpjpeg,dst=0.0.0.0:8888}'If you want more of a "proper" video stream (whatever that means) one good choice is to use Icecast[1][2]. It makes it pretty easy to set up audio and video streams and publish them.
[1]: https://icecast.org/
With a netcam the PC is only needed to set up the netcam, then the netcam streams by itself, connected directly to your network, the PC can then be turned off.
Either way you would be opening a port on your firewalls/routers to match the one you select for your camserver-PC (or netcam), for viewers to access the cam at yourIPaddress:port by using a media player like VLC or even the old Windows Media Player, which accepts a specific port for streaming media from a numerical or named IP address.
Basically you use the "port forwarding" features of your router to allow the internet WAN to connect to your private LAN through that one specific port only, where the camera stream is present. This is considered a "pinhole" in your firewall.
The viewing user does need to use a media player that has the proper codecs installed to play the format that your particular cam is sending. With encoding software like OBS you can choose to stream other formats besides the native cam output if you want.
[1]: https://github.com/aler9/rtsp-simple-server [2]: https://github.com/video-dev/hls.js/
basically use ffmpeg to make an m3u8. use caddy to serve the video files and the html/js. videojs will rebox the m3u8 for your friends using chrome/android.
A fluke would be me, an unskilled player, throwing a basketball and getting a lucky hoop. But getting a basketball through the hoop is not an unusual example of anything.
They discuss this, realize there's absolutely no chance of this working, so just agree that she'll throw it, and they'll cut to the ball going in. So she goes and takes the shot and... the ball goes in the basket.
There's video of this online that includes the cheers from everyone in the crew who saw it happen. Just don't ask her to do it again.
The Longest Running Web Cam, Set to Go Offline, Has Been Saved
https://www.smithsonianmag.com/smart-news/longest-running-we...