Almost all old rangefinders were quiet, ditto for folders and TLRs - it wasn't in any way Leica specific. SLRs, on the other hand, can be rather noisy because of the mirror slap. Pentax 67 sounds almost like a weapon.
The reason for it being rare here in Finland is the lack of demand.
Most horses that are put down would be perfectly fine for human consumption, but slaughterhouses do not buy them for the aforementioned reason. The primary consumer of horse meat in Finland is the sausage industry, and they buy cheap South American meat by ton.
IIRC it was also common for the engine to follow the steering column into the passenger compartment to polish off the driver and break the passenger's legs in case they hadn't been maimed yet.
Not true, neither of the founders died in a car accident.
Volvo had a very strong safety emphasis already in the '50s, introducing many firsts in the automotive safety field. In that decade they introduced shoulder belts as a world first and padded dashboard as an European first (Tucker had this already in '40s but only 51 cars were ever made).
"Another change since the original OSes were initially being built is the need for security"
I do not know what's referred to as "original OSes" but many old operating systems had actually pretty decent security architecture. MULTICS and VMS, for example, and many others too.
It's true that some did. I was more referring to the history of most of the major OSes we use today and specifically when it came to the first microcomputers. Generally when they were first being used (and the OS was being expanded) security was not much of a concern.
Back in late '90s a friend lived in a student dorm which had a then-fast 512 kbps Internet connection. It was heavily firewalled - UDP only to ISP's nameservers, TCP only to ISP's web proxies. ICMP was passed anywhere, though, so he wrote a small program which encapsulated a TCP stream in ICMP "host unreachable" reply packets, IIRC. The other end of the tunnel ran on a machine at the place where he was interning as a junior programmer. Debugging the program was slightly painful because he couldn't obviously be at both ends of the tunnel simultaneously, but he got it to work in a couple of weeks. It wasn't very tolerant of packet loss - IIRC it didn't have any mechanism to resynchronize the connection if there was any, but instead there was some method of reinitializing the connection. Anyway, running SOCKS on top of all this made the ISP-crippled connection usable in a normal manner.
Ahh, dorms are often the first place people start experimenting with this kind of stuff :)
I remember doing something similar at a friends dorm. They had a filter to only allow HTTP/HTTPS traffic via their proxy, so I used some HTTP tunnel tool to push a VPN connection through it.
It was pretty weak but it worked for basic usage. I remember having a real hard time figuring out what was causing VPN connections to drop intermittently. That's how I learned about HTTP keep-alives.
Is the obligatory comment attacking his character on every thread about him really necessary? How about discussing the solution he is actually proposing?
It's relevant because everything he's done up till now isn't anything technically innovative, just mainly ways for him to make money and promote himself as some kind of Internet hero, which is is not. This project will be more of the same nonsense.
