It all depends on who you are optimizing for.

• Parents with kids would do better on standard time, because they have to take their kids to school before work.
• Everyone else with a 9-to-5 job may do better on DST, assuming a short commute distance, because sunrise at 7:20 instead of 8:20 just adds useless time before the morning commute, while sundown at 5:53 means driving home before dark.

There is no one correct answer, because which one fits your circadian rhythms better depends entirely on what time you wake up.

Can't tell if we should moderate the article as Troll or Flamebait.

Commenters have already pointed out the dishonesty of the prose based on their own published stats.

"You are a poor scientist Dr. Venkman."
-Dean Yeager

Yes, I'm enabling the clickbait by commenting.

JPEG-XL is a good format but I just realized yesterday that Google Docs on Android doesn't support inserting a webp image a decade after Google was pushing it. I had one from a website and needed to run it through imagemagick first.

Android supports it, all the apps using android image primitives supoort it, but one of Google's flagship apps still doesn't.

We used move much faster thirty years ago. If an app supported say GIF, PNM, and TGA when JPEG came out it was supported in the next release.

Hopefully this round will be better. It's probably a management problem ... maybe they will listen to their chatbot since they don't listen to their engineers.

I live in B.C. and applaud losing the time change, but think the choice of time zones going forward wasn't the best.

I'm expecting major buyer's remorse this winter when people realize that the sun sets at 5 in December and January, and doesn't rise until 9.

...laura

I don't know the protocol but old phone headsets had a 2.5 or 3.5mm jack with an extra ring that got you play/pause/hook/next/last.

Hypothetically that could have been implemented. I had a collection of Alexas that got binned as soon as they got caught spying for police so I never got that far. ESP32 is better for nerds anyway.

One thing Australia does right is a statute naming removal of features as a violation of contract requiring full refunds in these circumstances.

It's hard to believe that a Jordanian teenager learned the PeopleSoft vendor integration API well enough to exploit it.

Probably somebody whose dayjob is related.

Maybe he was just Vibesploiting, but it seems less likely.

AM radios in cars only cover the small intersection of people who don't already have an emergency kit containing an AM radio, but do happen to be in a working vehicle during a disaster.
It's useless for anyone who's outside of a vehicle for whatever reason - eg vehicle is damaged, out of fuel, had to be abandoned, or was not available nearby when the disaster struck.

And what about people without a car?
Also if you've been forced to abandon your car due to the disaster, there goes your radio too since you can't easily remove it and wouldn't be able to operate it even if you could. A portable radio can be taken with you.

Depends on the nature of the disaster.
High winds can easily destroy solar panels.
Thick clouds will massively reduce the amount of power they can produce.
Thick smoke would be even worse.

At least he didn't write "I hope you are well"...

AM radio has very poor audio quality, you wouldn't want to be listening to music that way.
And your problem is trying to stream. Modern phones can have more than a terabyte of capacity, more than enough to store anything you'd want to listen to at a reasonable quality level.

I believe you misspelled "slower than molasses in February".

If they break into a car and the police look at the footage on the dashcam and see that they've kept their license plate out of view, but they are able to cross-correlate it with other cameras and figure out the plate number, then figure out where they drove that car, where it ended up parked, who got out, where they went, etc., then it can make arrests possible where it was not possible previously, making it *massively* more likely to be able to solve the crime.

The problem becomes when it turns into "show us all the plates that were near that spot within a few minutes of that time", and thus a fishing expedition.

You're interpreting it in the context of typing "sudo" on the command-line granting a one-time permission. And the original statement from Apple (after correcting the "every -> very" error in the summary) makes it clear that this is *not* what is being proposed, so if that was the original poster's intent, then it was incorrect.

The way I interpreted the original sentence — "They're going to make it like sudo where when you give permission to a program to write protected files once it has it forever after" — is that they're going to make it like the sudoers file, where you edit it to grant permission to a program to do something, and it permanently has the right to do that... which is exactly what happens when you grant full disk permission, just with a dialog box instead of editing a file.

That said, I'm not sure if that's how the original statement was intended to be interpreted. It was a bit confusing. :-)

Nope. And this is why I object to the phrase "censorship is bad". *Unreasonable* censorship is bad. But not all restraint on speech is bad.