That would have been around 1984 or 5 I think. So yes, it was "usual" or at least published by way of a software product by around the mid 80s. So certainly by 1991 it was not new. I don't believe I invented the idea either - in any case, it was certainly an idea that would have occured to anybody "versed in the arts" back then. Back then the process was done by phone. You generated your unique id, called us and we have you a hashed key to unlock the functionality derived from your generated key.
Just for amusement, this was done in Australia too. Not that that means this earlier system should have been known to the patentee.
But surely to be a seizure implies loss of use.
Not arguing the judge should have allowed the practice. Just wondering about the use of terms.
Of course, the English drive on the right side of the road (which is to day, the left) so the passing lane is the right hand one.
In Australia I don't think there is a law but at least one person has been booked for "obstructing traffic" when failing to get past in a reasonable manner.
If you think about the inheritance tree (in C++ if you like) then all methods are inherited. There are no synthesized attributes. On a general tree, attributes can be both inherited (they flow away from the root) and synthesized (they flow towards the root). These terms were original introduced by Knuth, I think, a long time ago in a context far far away.
In a language like C++ you have to know what type has the synthesized attribute to do a dynamic cast, so you cannot write a routine that will work with any type that has a given (set of) method(s). So you end up forcing all the methods used by some set of classes down into a common ancestor (perhaps, in C++ as pure methods), which is a nightmare or even impossible if the common base class is not in a subsystem you own or can convince someone to change.
One way to handle this in a statically typed language is with interfaces. You define a parameter as supporting an interface. This can be (partially) checked at compile time at the call point and assuming your language allows checking at runtime, never converts a compile time fail into a runtime fail because you would otherwise have had to do a dynamic cast that would itself only fail at run-time.
It does have the advantages that more of them fit in the bedroom and people don't look at you funny.
Certainly such systems of government (where the individual is subservient to the state) have existed and still do, and there are those who want to restore them, often but not exclusively in the name of religion. A lot of blood has been shed over the last three centurys to overthrow such governments, and no doubt will be again. Trying to stop things getting to that point by defending the US Constitution against depredation from short term expediencies makes a lot of sense.
The problem with autocorrection is they frequently autocorrect incorrectly and often the "corrected" sentence is less understandable than the mistyped version since the corrected word is no longer recognizable as a mangling of the intended word.
I bet it can't tell the difference between me, sitting at the kitchen table watching the Football and my wife sitting at the breakfast table with her back turned.
I bet it can't tell that I am reading, not watching.
How does it distinguish a large dog from a small child?
If it uses infra red it can at least distinguish a human from a cardboard cut-out of the Duke of Edinburgh! I have seen award ceremonies have trouble with that one, so I guess that makes it smarter than some humans.
We see something similar with TicketMonster; charges are often around a quarter to a third of the total cost of tickets even though the preferred method of delivery is electronic; they even tack on a bit extra for the privelege of printing them on your printer, and they tack on a bunch of advertising while they do it, costing you excess ink.
Content can be delivered electronically cheaply, but its delivery is currently expensive because a handful of companies have cornered the delivery.
This is definitely a model that content providers need to break up, so Murdoch clearly does have some understanding of the way the net works and why it is bad. Unfortunately he does not seem to have worked out how to combat it. His answer that "we don't make hardware" is exactly the wrong answer - he should be leading the effort to either open up Kindle or come up with an open replacement.
In any case, devices with cases that cannot be opened undetectably have been with us a long time as have those devices that you stick on the inside of a box to detect rough handling.
Always draw your curves, then plot your reading.