Too bad for "standard forensics" that the passcode is mixed in with a hardware-specific key baked into the SOC. So you'll first need to be able to run arbitrary code on the individual's phone itself in order to keep guessing beyond the limit. That's going to require a significantly more intrusive examination.

Self incrimination has never applied to physical evidence that the individual has in his possession, it only applies to things that are "testimonial" (quotes because this is a term of art). After all, the 5A specifically talks about being a witness against one's self, not about providing evidence. See also Fisher v. United States, 425 U.S. 391 (1976), Schmerber v. California, 384 U.S. 757 (1966) and United States v. Wade, 388 U.S. 218 (1967).

The classic example is business or tax records related to fraud prosecutions. An individual served with a valid order cannot refuse to turn over documents because they would tend to incriminate him, that doesn't make sense. You can't force the individual to testify to anything, but you can compel them to produce physical objects that you have probable cause to believe are evidence relevant to the prosecution of a crime.

Another canonical example is a court order forcing an individual to provide a cheek swab for a DNA test. Again, not testimonial because it's not communicative in any way -- you are just talking about physical, tangible evidence.

Slashdot needs to get out of the nineties and into the 21st century.

You can get your old account back if you can remember what your email address was. Send a note to help@slashdot.org.

I'd lost my account and they were very helpful about it.

As to your surgery, LISTEN TO THE DOCTOR!!! Helping that one person could prevent you from helping others in the future. Oh, and I empathize; I had a vitrectomy in 2008. Not the least bit fun.

NFC implementations (should) be interoperable unless somebody screwed up implementation to spec; but that promises nothing about compatibility for anything built on top of NFC.

Right now, ISO 7813 mag-stripe cards are nice and standardized; but that only gets you as far as having the reader hardware work. Whether your card will be accepted by a given vendor is an entirely separate matter governed by some ghastly pile of contractual arrangements.

Ah, that's just because today's ultra-high-density platters require high-coercivity materials in order to adequately maintain the magnetization patterns that store the data. Low coercivity magnetic media just don't work at those densities.

It'll never quite stop being weird that Commander Keen, cartoony platformer, is what the guys behind Doom and Quake were working on in their early days....

It is a matter of taste; but the proliferation of 'widescreen' has really made multiple orientation setups more attractive. In particular, the ubiquitous 1920x1080 is cheap as dirt and nice and wide; but actually throws fewer vertical pixels than a nasty old 1280x1024 17' from about 2001. If you read or write a lot of text, or code with reasonably short lines, taking a cheapo 1920x1080 and rotating it gives you a 1080x1920: this is handy because it's still wider than 1024(so even old and horrible programs/layouts generally won't break, since anything that old and horrible probably expects 768 or 1024 pixel wide screens); but provides more vertical resolution than even substantially more expensive monitors in their native orientation.

I prefer my 'primary' monitor to be unrotated; but the amount of vertical resolution you can get for the money, without totally sacrificing width, from a rotated secondary monitor is pretty compelling.

In this case, you might want to go after the vets before the doctors...

It's not an accident that they were looking at agricultural workers (rather than, say, elementary school teachers, who would be seeing the worst of it from antibiotics-for-the-sniffles patients), nor is it an accident that there are 'livestock-associated' drug resistant strains.

Aside from price, which makes accepting multiple monitors rather compelling(you can get physically big ones for relatively small amounts of money, because of TVs; but if you want resolution the cost goes up fast and things really start to misbehave if you go high enough that DP MST or the like is required to drive the thing), it mostly comes down to how good your windowing system is at tiling and how well applications that expect 'full screen' can handle playing with others.

A good window manager makes carving up a single large monitor into chunks suitably sized for your various programs easy and painless. If you are enduring a less obliging one, it can be a fairly ugly business, actually less pleasant than getting some help from multiple physical displays, which are more widely respected even by poorly behaved programs.

That said, the 'two side by side, giant bezel in the middle' configuration is not my favorite. A larger primary screen, with ancillary screens on one or both sides gives you plenty of room for assorted lesser windows; but also avoids annoying bezels in the center of your field of view.

You don't choose between workspaces and physical screens, you just have multiple physical screens so that each workspace can be even larger and more pleasant to use...

You do eventually run into diminishing returns; but being able to display more than one monitor worth of stuff simultaneously definitely has its uses, and is something that being able to switch between workspaces, be the transition ever so elegant, cannot replace.

Given that 8 was the "Just because it's called 'Windows' doesn't mean it needs a functional windowing system!" release, It's pretty hard to argue with them.

Maybe some of that works on touchscreen laptops; but 'metro' is a tragicomedy on any monitor configuration worth using.

"It's not enough getting a free ride off of developers building great software, we want to shove our roadmap down their throats and get them to work harder for us â" without having to pay for it, of course."

Looks more like "We want to figure out how best to coordinate and share that portion of the work that the people whom we pay to develop software for us, do on free software." (Though they're not using that dangerous word "free", of course.)

"Free" or "open source" doesn't mean no one is getting paid to develop it.

In addition, Tesla(whether or not you see this as an improvement is a distinct issue, it simply is so) sells cars much more like an enterprise IT hardware vendor sells hardware: at least within the warranty period, there is very much an ongoing interaction between the hardware and the vendor. System health information gets sent directly back, on site techs with specialized parts and firmware get sent out and so on. More traditional car companies are closer to buying a PC: the dealer will offer (often absurdly priced; but available) maintenance; and the vendor may become involved with certain warranty or recall cases; but they are otherwise largely out of the loop, with third parties handling the ongoing interaction with the hardware.

Something has to provide coordination and theatre-level intelligence for all deployed Highlander batteries, no?