I don't think volume explains it completely. The most expensive components in an IP camera (camera, network, controller) are mass produced in incredible quantities already, whether it's for smartphones or dashcams or Gopros or point and shoot cameras, and stuff like smartphones with far more technology included (super hi res touchscreen, LTE modem, battery, flash, vastly more complex software) are cheaper than all but the junkiest 720p IP cameras.

*Components* isn't the reason, the components are dirt cheap. I don't even think assembly is a big reason -- security cameras are ubiquitous, so assembly, case parts, etc. should be widely available, too.

Really the closest you come is game cameras, which mostly are missing the networking part but kind of make up for it in complexity with motion sensing.

IP cams' web interfaces are one of the few places, though, where it's nearly ubiquitious.

I'd say it has more to do with junk Chinese electronics compaies all buying the same core tech package and minimally changing it to suit their branding.

What's truly obnoxious are the perfectly usable cameras which haven't upgraded their firmware to ditch activex for javascript.

I think there's a ton of money being dumped into the walking dead.

When my mom was at stage 4 of metastasized breast cancer, we had a family meeting with the oncologist to discuss my mom's situation. When asked what -- if any -- chances she had for life extension (not a cure, but more than 12 months) he was totally equivocal about it and was basically looking to start another round of chemotherapy. I felt like he was just looking for another round of payments before she died. They give you the thinnest hope to try to get you to keep using their services.

I've heard similar stories before from other people with older relatives, very sick and unlikely to every recover in any meaningful sense of the word yet the doctors insist on expensive and invasive treatments. The only explanation I can think of is that it's good business for them.

Yep, there are a lot of flashing lights and beeps sending code in the computer world. I still hear phones using "... -- ..." to indicate an incoming SMS.

OpenSSL has first-to-market advantage, and anyone who hasn't evaluated the quality differences will choose the simpler license. Plus there are other alternatives, like Amazon's new SSL-in-5000-lines which is also gift-licensed.

The time for OpenSSL to dual-license was when it was the only available alternative to entirely proprietary implementations. That might indeed have funded a quality improvement.

I don't know a thing about the quality of GnuTLS or the Amazon thing. I've seen enough of the insides of OpenSSL to know it's not pretty, but am not a crypto guy and this don't work on it.

Maintaining FIPS compliance did not make anything easier. It's essentially a prohibition on bug repair, as you have to recertify afterward. But the people who wanted FIPS were the only ones who were actually paying for someone to work on OpenSSL.

I don't think any of the other Free Software projects ever tried to be FIPS certified.

If you are one of the infringed parties, I'd be happy to talk with you about what your options are. bruce at perens dot com or +1 510-4PERENS (I'm not there today, but it will take a message). I am not a lawyer but I work with the good ones and can bring them into the conversation if necessary.

As a community we've managed to almost completely ignore that because of their use of dual-licensing, MySQL made 1.1 Billion dollars after 9 years in business, and that for a database that was written by one person, and the code base remained available under the GPL.

IMO, 1.1 Billion dollars is pretty damn impressive. Especially if you get paid that to make Free Software. Heck, sign me up!

Oracle was a bad actor, and Monty is now leading further development of that same code base under the GPL. But it did not have to be that way.

How do you prove damages or have the right to settle violations if you don't have copyright?

If you have been doing enough work to justify getting paid for the software, you have an ample amount of your own copyrighted work to base your claim upon. If you haven't done that much work, what are you suing for?

You can also get a grant of the right to sue from your contributors. You can include in the agreement how you will apportion damages: for example you could take the ratio of your lines of modified code checked in vs. that of contributed code checked in, and give that portion of damages to FSF.

So when this trusted friend claims the $14m and then decides to keep it all, what do you do then? Hey, he's not sharing the money from the scheme I rigged?

It sounds like the perfect crime...from the trusted friend's perspective.

You do have to get either copyright assignment or the right to relicense from your contributors, if you have contributors, or the whole scheme doesn't work. But maybe you get enough money to pay them some.

Yes, writing Morse Code Software is one of the creative and educational things you can do with Morse code.

It took me 60 days to get to 20 WPM, working for a long time every day.

In contrast, it took a lot less time to write an interrupt-driven, terminate-and-stay-resident Morse Code sounder program in 6502 assembler. And I learned the instruction set, too.

I'm not saying you don't want to do either. It just doesn't belong on the test.