More likely is that 6 lines was enough general text where Richelieu could inevitably find subset that could be taken out of context from the whole where the inference would be contradictory or cross purpose to the original text.

For example:
One may write: The assumption that I would kill a man is preposterous.
After omissions of text at the beginning and end: I would kill a man.
The argument: Were these words not truly written by your own hand?
The result: An innocent man goes to the gallows.

Self defence is a core right independent of the second amendment. SCOTUS upheld that the right to bear arms is not exclusively tied to militia service.

The second amendment says nothing about defending yourself. It is simply about being free from harassment by government in owning and carrying 'arms'. It says nothing about using them against another person, and it seems to imply that it is for the purpose for maintaining a well regulated militia. The definition of 'arms' is intentionally generic so as to not exclude any particular type or category of 'armament'. Obviously it has been watered down by various States and case law, but not yet to the point of a blanket requirement that it only apply to a self-contained physical apparatus.

Beyond that, the concept of self defence is founded in common-law where it is deemed reasonable that you should be able to defend yourself against an attacker to prevent or minimise injury. Further to this, if it is legal (and reasonable) for you to be carrying a weapon (or tool) at the time, then using that weapon (or tool) for self defence is also a valid legal defence to prosecution of the self-defender.

However, you are correct in that retaliatory strikes are not self-defence. And whether or not a weapon or other tool is used to perpetrate the act is inconsequential to the fact that you then become the offending party.

Even more interesting would be if they start hybridizing drive with different SSD types. eg. 128GB of SLC high reliability high write count Flash combined with 1TB+ of ECC protected MLC/TLC storage. The older more static data migrates to the MLC/TLC storage, and the immediate data uses the SLC side of things where re-writes are far more common. This would of course be in addition to a capacitor or battery backed RAM cache.

A good controller could periodically scan the array in the background and rebuild any areas that start to accumulate errors. That way, drive failure becomes all about catastrophic hardware/controller failure rather than death by a thousand cuts as cells degrade.

This is similar to how high quality SDCards have small sections of high endurance (1M+ rewrites) EEPROM that is used for the internal remapping blocks and other fast changing blocks (eg. FAT).

I know it may sound a bit crass the way it's worded, but positive and negative reinforcement are extremely powerful motivation methods for both animals and people.

Reward charts are a long time proven method to keep kids motivated without using punishment. Punishment is also very useful, and like positive methods must be tailored for the recipient. Not all people respond the same to positive things, and punishment (or fear of it) is not always beneficially motivational.

Things like ClassDojo are a convenient 'digital' way of having a child 'carry around' a reward chart that can be seen/used by both parents and teachers. Functionally, it is quite effective.

However, as the summary points out, data mining and exposure of otherwise private information pertaining to a child is a problem. And something that needs to be addressed.

No, the prevailing ideology around here is that once data has been made public (ie. publication), it is no longer private and therefore cannot be 'taken' or 'stolen'. And that the action of copying this data doesn't necessarily cause a net harm to the original creator(s) of the work.

However, data that is private can be stolen and that is why this type of thing is frowned upon. Just because some 5 year old kid is in some private database does not mean that it is now free for everyman and his dog to mine or archive. Likewise to your private photo collection, your conversations in your living room, your bedside diary, etc.

TV images of when you ran through the town square naked? Not private either.

See the difference between reality and your straw man?

A brief history of thyme?

30 years late, 30 years more. Then another 30 when that's all done.

When the say war, they mean "war".

That assumes the target doesn't change speed or direction in a non-predictable way. Otherwise, the missile will be significantly off-course and potentially millions of miles away unless it fires up its correction thrusters early enough.

I'd be more worried about all the super fast micro-particle engine ejecta that are whizzing through space. Chasing another ship with a reactionary drive would be quite dangerous as you'd want pretty powerful force fields to stop your ship or missile getting perforated as the target ship manoeuvred to protect itself, intentionally keeping the attacking missile and/or ship in the hard to detect ultra fast moving micro-particle ejecta field.

I am not a number, I am a free man.

Oops, my bad, I forgot we're talking about somewhere in the USA.

And now the 97% consensus have updated their models to include the new data. Prior to that discovery, their assumptions were based on what they previously knew or thought to be true. Once including that new information, their assumptions have been updated and the vast majority now assume differently.

But, most importantly, they are still aware the difference between what they hold as assumptions/beliefs and what has been observationally confirmed.

The last one didn't go so well, so we are repeating the experiment here on this planet which is next in orbit and slightly more distant from the Sun.

Maybe they are just verifying the remote telemetry that had already been sent.

"McCoy to Enterprise. 85 degrees Celsius!!! Celsius man! Beam up now!!!"

Meanwhile, back in the transporter room...
"Ooops. My bad. Someone in the previous shift must have changed the telemetry readout from Fahrenheit."

Maybe it was, and then they bypassed that phase of society by edict.

"Hey Redshirt! Get off that communicator and help us deal with this ugly alien, or it's going to end badly for you!"

"Oh crap, we just lost another Redshirt! Enough of this shit, from now on only officers get to bring communicators down to the planet surface."

Security of the transport is not what is at issue. The security of the entire stack needs to be evaluated for a weak link further down the chain before security could be claimed to be a non-issue.

You are right though that the API probably isn't completely ready and/or Apple want to release their apps first. Probably not a bad idea while they iron out any problems before all and sundry spew forth apps. It is much easier to deprecate an API element to fix a major security or other problem when your own implementation is all you have to worry about breaking.