And if you want to tank it without overtly tanking it.

“We will need to establish a review and governance board to establish standard data structures and reporting that can be used to drive the initiative.

It will need to be cross team and cross specialty so we should start by establishing a group to identify those people so we can proceed”

A year later and you’ll be lucky if they’ve even picked out who can be part of the review process let alone agree on some convention and adjusting their tooling and processes to make that work.

I was thinking of the term salinity.

There’s also heat exchange so you’ll have deep sea vents where there could be all kinds of caustic stuff and/or minerals.

So it wouldn’t necessarily be fresh even if that stuff wasn’t saline

And utilities for identify the eventual duplicates to save space (while still ensuring you don’t have only 1 copy that can be corrupted)

Like anything else it’s always trade offs.

No, no. I’m looking for BWILA’s

Noble Knight: Fine, you continue to drive and see a sign that says 2 BWILA’s 15 miles.

Scoofa! I roll for mileage. 19, do I make the exit?

Noble Knight: sigh, yes.

Could even be a loose stick of ram.

Psych

If I recall correctly it’s important to be running ECC memory right?

Otherwise corrupter bites/data can cause file system issues or loss.

I see a lot of good answers here but let’s try it from another angle.

How do we get randomness from a function or formula?

For starters let’s setup a few simple rules.

Every time our random function is called we’ll

• Take the last output from a variable we call LAST_RESULT
• If there’s no value in LAST_RESULT we’ll assume the value is 1
• We run a set of calculations storing the value in a variable we call X
• We store the result of these calculations in LAST_RESULT
• We return this new “random” number.

So let’s call it.

> Random()
Since LAST_RESULT is undefined SET LAST_RESULT to the value of 1
Set X to the result of this calculation 
   (LAST_RESULT+1) * 3

X is now 6

Set X to the result of this calculation
   (X + 7) / 2

X is now 7

Set X to the result of this calculation (rounding to the nearest whole number)
   X/LAST_RESULT

X is now 7

Set LAST_RESULT to the value of X

LAST_RESULT is now 7

Return the value of X as the result 

Result is 7

Ok. So let’s call it again

 > Random()
Set X to the result of this calculation 
   (LAST_RESULT+1) * 3

X is now 24

Set X to the result of this calculation
   (X + 7) / 2

X is now 16

Set X to the result of this calculation (rounding to the nearest whole number)
   X/LAST_RESULT

X is now 2

Set LAST_RESULT to the value of X

LAST_RESULT is now 2

Return the value of X as the result

Result is 2

And if we call it again we get seemingly random results

Random() Result is 4

Random() Result is 3

But the next time you run it you’ll get the same results in the same order. 7, then 2 then 4 then 3

So what you need is something to “seed” the random number calculation.

Something like

SetRandomSeed Set LAST_RESULT to the current second of the day

Then when you call Random after this it starts with that as the prior results and gives seemingly random results.

Of course my calculations are rough and probably fail/repeat after so many calls but it gives you an idea of how this works.

So the trick is to get noise for the seed. That could be the number of non leap seconds since 00:00:00 UTC on Thursday, 1 January 1970 (Unix epoch)

Or the temperature reading of a CPU chip.

Maybe it’s the ratio of red vs yellow from a camera feed looking at lava lamps.

Or the current users average typing speed.

An additional note. Many of those would not be “cryptographically” secure for encryption because they can easily be determined by a third party. We all experience the same “Unix epoch” within a few milliseconds if our system clocks are properly set for example. Or monitored from afar and reproduced (hacked webcam shows they had just typed the following letters in the previous 27 seconds that we know the “algorithm” uses, etc.

Air only has so much resistance itself. High enough voltage and the closest path to ground is where the charge will go.

Just like with Lightning

It’s designed to make sure that the contact point with the back plate is reinforced.

That’s the point you don’t want to have fatigue or stress during shipping, etc since it breaking off there when it’s plugged into your wall would be a pain.

I suspect it’s mainly there for the shipment from the cord manufacturer to the company that made the product and there’s little benefit in removing it on their end when they can then ship it, cover and all, to their end consumer.

Jack stands too. But not harbor freight ones

Pretty good for anything that can kill you if it fails. Even beyond power tools.

So, for example, yes to drill. No to compressors, jacks, etc.

Well said. It seems to all be about satisfying our expectations.

Or when expectations are subverted but then satisfied in a different way (jokes, puns, etc).

But basically confirmation of our pattern matching being right.

1,2,3,4… I will now say more.
5,6,7,8… I will not hesitate.
Satisfying

1,2,3,4… I will now say more.
5,6,7,8… I will not delay.
Frustrating

Exactly. And in such a scenario it becomes an issue for Kinkos

Issue here is that what’s in a safe deposit box isn’t also being shared/distributed. It is locked away.

If, however, they made copies of the contents of a box and put it in other boxes … and it came out somebody used that for CSAM then there probably would be some kind of liability.

Besides CSAM there’s also copyrighted material, etc which section 230 kind of covers but even then gets tricky since there’s a duty to respond to DMCA takedowns in order to get safe harbor protections.

Wait…wait… we need somebody from legal on this call

Libby and your library card.

Personally since I use touch typing being able to hit ctrl-c,v without looking works best for me. Anything else would require me to shift my hands too far away from the “home row” and slow me down.

“Hamish, what if we coat it with scratchy sand?”