The simplest and most likely explanation is that the license ran out and the copyright owner wanted too much money or some other onerous condition, so google decided to wait until the next satellite pass when they'll get all the imagery.

Unanalyzed raw video. Internet noise. Those would qualify as, "a whole lot of garbage that someone could possibly, maybe analyze to make some statistical inferences about conceivably sensitive data."

There's not 10 petabytes of sensitive data in all the world. 10 petabytes is enough to store a copy of every movie and television show ever released to DVD plus every book ever written in any language on Earth.

What they captured was some sensitive data and a whole lot of garbage that someone could possibly, maybe analyze to make some statistical inferences about conceivably sensitive data.

They sabotage themselves just fine with user-hostile security implementations and bloat bloat bloat.

I'll bet. His case has less than no chance in court.

It's good. Until it isn't.

I'm a computer scientist with three decades of expertise in computer networking. There's this one AI-based job board that keeps trying to match me with delivery driver jobs.

Designing a structure with withstand a major act of war basically means digging it far enough underground that nothing can reach it. It was a stupid rule.

You have to check when they're available anyway. Even where people actually work "customary business hours," they take time off for things like doctors' appointments and childrens' special events.

I vote for option E: Everybody switches to UTC.

Local noon on the U.S. pacific coast will be 20:00 instead of 12:00 and the office day will start at 17:00 instead of 9:00 am. But in trade, I never have to do any mental gymnastics converting for someone else's time again.

For future reference, Slashdot is an international site, so when you post about something specific to a single country, something about the post should give the reader some idea which country.

Correct, nothing worse. But Rust has to be *better* than C at something for it to be a better choice, because without the memory safety guarantees, C is faster. C is also much better suited to tasks which impose structural order on byte buffers without moving data. Which happens a lot at the system programming level.

If you can write it with an efficient run time in Rust without using the "unsafe" keyword and without relying on a library that uses the "unsafe" keyword then you've generally identified a use case where Rust is a better choice than C. If you need the "unsafe" keyword or have to write convoluted code to work around its absence, C is likely still a better choice. The kernel has both use cases.

First off, that's not even an article about Internet infrastructure, it's an article about open source software.

Second off, when you use open source software, you own the copies you're using. That's the whole point. If it breaks and the original author isn't around, you hire someone to fix it or replace it with different software. That's how it works. And all of the software licenses deemed open source are structured to make it continue to work that way, with or without the original authors.

This information is useless without knowing what the passwords were chosen to protect.

Let's face it: the password to my netflix account is not very important to me. If it's hacked I suffer a minor inconvenience at worst. What would be inconvenient for me would be if netflix forced me to do 2FA or some other complicated thing in order to use their service. That inconvenience would drive me toward cancellation.

The password to my bank account IS very important to me. I picked a much better one there. And of course the password to my primary email box is critical, so I chose a careful password there.

You mean caning treatment. The word you used means stuffing in a small metal container.