I have never gotten one of these calls. But I have gotten a few calls like this:

[Phone vibrates. I see the non-local calling number. Reject and block.]

That's the new, lazy version. Until a few weeks ago, I had many of these:

[Phone vibrates. I look at the non-local calling number and wonder who that could be. Google the number and apparently every non-local number that ever calls me, is associated with robocalling. Reject. They call again a few days later. Reject and block. Then a few days later I look at my Visual Voicemail which my shitty Galaxy S4 software never tells me has new entries until I refresh it, and some actual human speech may happen.]
ME: "Fuck."
[And I see they left a few messages containing nothing but silence. Delete.]

But that second scenario doesn't happen anymore. Robocallers have successfully trained me.

(I still do things the classic way: filesystem on lvm on luks on mdadm. not using ZFS yet.) I'm not sure it's exactly about what's required.

Consider wear leveling on SSDs. Only the filesystem really understands which blocks need to preserve data and which ones are don't-care. So to do SSDs right, it needs to pass info about unallocated storage down to the volume manager, whch then passes it to the encryption, which then passes it to the RAID, which then gives it to old-school "real" block device (which then passes it to the wear-leveling firmware, I guess). Sure, that can work. But when the filesystem can talk to the physical block device, it's easier. If you're writing block devices that implement things like volumes and encryption and RAID, from your PoV, things that are allocated vs not-allocated are totally different than how the filesystem sees it. To you, a block is just a block and a whole bunch of ioctls are totally irrelevant and not related to what you're working on. You're going to find this type of information to be pesky and you might not handle it right (or more likely, it takes a long time before you handle it at all). And in fact that has happened a few times, where certain block devices' feature set lagged a bit, behind what people with SSDs needed.

I suppose another easily-contrived example would be if you have a few gigabytes of data on a few terabytes of RAID, and need to [re]build the RAID. If your RAID doesn't know which blocks actually have data, then it'll need to copy/xor a few terabytes. If it's a unified system, then it can be complete after copying/xoring a few gigabytes.

..contracts requiring NDA's that now allows customers to review secret details of products or company practices on public forums.

Can someone who favors this, explain why this might be a good thing instead of a bad thing? Maybe an example? It sounds to me like endangering such a (seemingly, to me) bad practice might be an intended consequence, not an unintended one.

I can't even see how a review made under an NDA might be useful. The premise is that the reviewer is withholding information. "The spaghetti was excellent. [censored]I am prohibited from saying anything about the sauce.[/censored]"

I started trying to think of situations where a person can have a wrist-worn PC but cannot have a handheld PC with them -- situations where people are constrained for some reason.

The obvious thing most people come up with, is where it's a natural or convenient constraint. You don't want to be holding something extra while you're swimming or swinging an axe or climbling a cliff. I think the related applications are already well-discussed.

What about when it's an artificial constraint? I initially drew a blank on how such a constraint would emerge, until I considered situations where the served parties by the two PCs are different, so that the handheld (if one is present) might serve the user (or manufacturer) but the wrist-worn serves someone else.

Once you start thinking of situations where the user is in an adversarial (or seemingly or potentially adversarial) relationship with the owner then it gets easier to see the applications.

Prisoners, parolees, etc. It's not so much that you let them wear the Pebble or iWatch, as you make them wear it. And your prisoner doesn't need to be surfing the web or otherwise doing things where the PC needs to communicate things to the user, so many of the disadvantages relative to handhelds, become totally irrelevant. The application, of course, is monitoring: being an open spy for the government.

Somewhat similarly: children. Mom wants to know where you are, but isn't really interested in giving you Yet Another porn terminal. Quit fapping and get back to your homework at the libra-- your friend's house?!? Get back to the library!

Marketing. Get 'em cheap enough, and these could replace your "frequent shopper" cards as your cookie. Wear our wrist PC as you walk around our store and check out, for a 2% discount. The application is spying, again. And I guess as long as it has a speaker, it can play location-triggered ads. "Whoa, you just walked right by our delicious canned spoo and instant flarn. Are you sure you don't want some?" The idea here is that you could perform the application with a handheld, but the existing handheld PC would be too pro-user so it might not really play the ads out loud and it might report false travel data. So you want the pro-store computer to be a physically different one. Then it becomes a wrist-worn simply because that's smaller and cheaper ($10 instead of $100).

Sweatshops. The Slurm factory employees are spending too much time on bathroom breaks, and texting their friends. Well, the employee wearable PC doesn't do texts, and it delivers a shock after 90 seconds in the bathroom. If a supervisor ever sees you without your wearable, you're fired.

Jealous spouses. Hubby's "Love Watch" chemical sensors are picking up interesting volatiles: perfume? My, he sure is breathing hard and the GPS has him in a residential neighborhood, not at the mid-town office. Oh, those are just fringe use cases: everyone knows the real purpose of the Love Watch is that it instantly relays every time you speak "I love you" into it. (OMG, that last part is so sickening that I bet a variant of this product already exists today.)

Think in terms of why you might want to "plant" (though not necessarily with subterfuge) your computer on someone else, to be your agent rather than the wearer's. Those may be the best applications for wrist-worn PCs.

That was a TV show.

A work of fiction.

You shouldn't take what you saw seriously. It's not real.

What I'm trying to delicately explain to you, is that Heisenberg is still alive.

It's nonsense because most users, when they think about how a web app responds to an event, they're thinking of their "clicks" (or touches) rather than changing viewports. Changing viewports is a rare event (and therefore relatively unimportant) compared to pretty much anything else.

Saying a page is "responsive" when someone tilts their tablet, is like saying a car has "great handling" because the door handles feel nice whenever you stroke them. It's not that either is a bad thing; they're simply labeled stupidly and also imply things which might be false. And for whatever reason, some people resent terminology that is simultaneously stupid and deceitful. (Weirdos!)

Yes. Whenever people talk about "games" you know that's really just a secret code word for Dwarf Fortress.

Must be marketed toward the old geezer crowd or something.

No, you've got it exactly wrong. He's lamenting that they stopped marketing tape drives toward the old geezer crowd.

What's the obsession with...[computer enclosure flavor of the month]?

There was a cartoon in some [Amiga-oriented, I think?] magazine about a quarter century ago. It was a guy showing off a computer in an unusual case, saying "We figured out what users want isn't more power or increased applications, but rather, really cool tail fins."

If Yahoo ends up holding the private keys, then it's completely untrustworthy and useless.

Let's hypothesize that Yahoo does this the worst way possible, so we can play to everyone's fears. Let's say the users aren't even going to have the key on their machines ever, and instead, Yahoo explicitly announces they have your private key, and their server will do all the decryption and signing for you (your machine won't even be doing it in Javascript), and they're under US jurisdiction and therefore subject to CALEA and NSLs, and furthermore just to make things worse, let's just say that they even publically admit that they would happily provide keys to any government who asks, without even a warrant or sternly-worded letter. But when you ask 'em if they really mean every government, "even Russia?" they reply with "no comment" so you're not sure they're really publically admitting everyone to whom they'll give the key.

There. Did I cover all the bases? Did I leave anyone's pet fear out?

Sorry, let's add a few more things. Let's say Yahoo's CEO is a Scientologist, all their network admins are required to be either Holocoaust Deniers or Creationists, and every employee is required to have at least 25% of their investments in MPAA companies. The receptionists all have iPhones, the corporate mission is the next president of the USA must have either Clinton or Bush as their last name, and henceforth all their web ads will be for either Amway or Herbalife. All the interns are spies for Google and Microsoft and Chinese industries, except for a few which are spies for Mossad, FSB, or Al-Qaeda. The head janitor is being blackmailed by two unknown parties for his participation in a kiddie porn network, and the top sysadmin hasn't heard about Heartbleed yet, the top programmer (who bears the title "Grand Wizard" on his business card) doesn't believe in comments, their implementation of OpenPGP uses a 1938 Luftwaffe cipher as its entropy source for generating session keys, and the company weather station's thermometer was installed on a south-facing patio that gets direct sun all day long.

You may possibly harbor doubts about trusting this company. Yet in that situation, switching to Yahoo email would be more secure than what most people have right now, with plaintext email. So how's that "useless?"

Now all I have to do is get my father, my mother, my sister, my half-sister, my grandmother, my wife, and my assorted friends to learn what PGP is and how to read the emails I send them.

You jest, but don't you see how popular webmail providers adding insecure PGP implementations to their platforms would be a pretty good first step to doing exactly what you say?

What a silly feature. Just put "Cc: BackupDood" at the top of your email, and you get the same thing.

Where did it say in there that users would hand over private keys to a third party?

It's implied by the fact that it's webmail. Does your browser have an OpenPGP library? Does it check all the Javascript that it downloads and executes, against some repository's whitelist? You have to assume the key isn't handled safely, unless you can answer Yes to these questions. And a lot of webmail users expect the server to be able to search and that's obviously impossible unless the server can read, so it's not like the unsafeness stems just from potential trickery.

That said, the more interesting question is what social effect this might have. Even "bad" use of OpenPGP could start conditioning more people to being familiar with, tolerating, expecting PGP. Get into a better frame of mind, and better habits can come later. And with good habits, some security could eventually emerge. The security wouldn't be there for Yahoo webmail users, and yet some users might end up having Yahoo webmail to thank for it.

And let's face it, the barriers to secure communication are almost entirely social; we choose to have insecure communications. Anyone who is working on that problem is working on The Problem.

There are over 30,000 deaths in the US alone in automobile accidents; even supposing automated vehicles cut that number by 90%, 3,000 multi-million dollar settlements every year would destroy the automobile industry in the US.

3,000 multi-million dollar settlements sounds like a lot of money, but the 30,000 multi-million dollar settlements that we're already paying insurance premiums to pay for, is even more. Yet the system is apparently economically viabile even in 2014 when the costs are ten times higher. A scenario where where the accident rate is a tenth, is a scenario where insurance costs a tenth, so the total cost of a vehicle is somewhat less. This would be good for the auto industry, not bad.

If you tell someone they have a choice of two cars, one where they pay $70/month to State Farm (called "careless human's liability insurance"), and another where they pay $7/month to Ford (called "careful AI's liability insurance fee", because you're not buying insurance from Ford's AI, but rather, funding its insurance), that second one is more likely to result in a car purchase.

There would have to be a "work under this title" (something copyrightable) which becomes accessible by putting in the fuse. If plugging in the fuse causes their copyrighted AC-available icon show up on the dashboard, for example, then it'd be a DMCA violation to plug in the fuse without their authorization. Also, it might become illegal to manufacture or traffick or sell fuses without Chrysler's authorization, but that's subjective and subject to judges' whims (how they decide to interpret your fuse's primary purpose, commercially significant uses, Chrysler's marketing, etc).

But if all it does is enable the air conditioner (if there's no copyrighted work protected by it), then it's not a DMCA violation.

This wouldn't ever happen, though. Suppose you made your own copyrighted work and also had it become accessible only by plugging in the exact same sort of fuse. If you became "commercially significant" enough, then Chrysler's own fuse sales to their own customers would become illegal (devices that circumvent your DRM). It's for this reason that all DRM schemes need to be trade secrets or patented, to keep different copyright holders from using each other's schemes (or at least keep 'em from doing it without a contract to cooperate). That's why no one would really use fuse as DRM. It's not that they'd worry about their customers "hacking," but because they'd need to worry about someone (anyone!) coming and suddenly making their own business illegal.