"...a Chrome or Firefox extension that exports and uploads their recent search data..." Are they having a laugh?

But hours later he posted an update. "GitHub has told me they have raised this as a security issue internally and they are working on a fix."

"Humans know how to deal with a chaotic and constantly changing world" You sure about that?

Most definitely if you are concerned about a real risk of your data/identify being stolen vs a hypothetical risk of some government caring enough about you to steal your data.

The usual Slashdot inaccurate click-bait title.

Apple haven't removed "iCloud encryption", data is still encrypted both on route and in-situ. They have only removed "end to end" encryption, which prevents anyone (including Apple and authorities) other than the user from decrypting the data.

The vast majority of users haven't even heard of "iCloud Advanced Data Protection" (which enables e2e encryption), let alone enabled it (it is off by default).

Until you realise there are over 5 *million* private companies in the UK.

Or it didn't happen.

Seems like only yesterday they were complaining because they couldn't read encrypted comms.....

Doubt this will even be legal in the UK....

But here is ChatGPT's summary of the podcast transcript:

The podcast episode from SourceForge features host Beau Hamilton interviewing Steve Yegge, Head of Engineering at Sourcegraph, on the future of programming and the evolution of coding tools. Yegge, with a rich background in companies like Amazon and Google, shares his journey and insights on modern programming, highlighting Sourcegraph's shift to an AI-driven company. He discusses Sourcegraph’s products, like the AI coding assistant Cody and Code Search, emphasizing the growing importance of AI tools in simplifying and enhancing coding efficiency.

Yegge introduces the concept of Chat-Oriented Programming (CHOP), predicting a move away from traditional, line-by-line coding toward a block-based approach enabled by AI. He envisions AI transforming software development, making coding more accessible even to beginners by shifting the focus from syntax to larger structural concepts. However, Yegge notes that this shift will demand new skills like prompt engineering and managing AI-generated "hallucinations," or inaccuracies, in code.

Yegge also touches on the cultural impacts of AI within the tech industry, expressing concerns that companies and developers resistant to AI could fall behind. He provides practical advice for developers to adapt by enhancing their reading skills for better comprehension and prompt management.

In the episode’s conclusion, Yegge shares a sobering warning about cybersecurity risks, advising listeners to protect their assets as advanced AI tools could make scams more sophisticated. He ends by encouraging listeners to explore Sourcegraph's resources for more on CHOP and the future of coding with AI.

1. No, sorry but protecting against a bug in a kernel driver running in ring 0 with no address space protection is not possible. You would get exactly the same type of crash with a bug in a Linux kernel module.

2. Agree completely

The most annoying thing is that the UK has decided to inherit this. And we voted out FFS.

Except, that the last option is:

"or a speed control function in which the speed of the vehicle will be gradually reduced."

So it is potentially *not* just an indicator, but a very annoying actual limiting function.

And yes, you can disable it *for now*. But what happens in (say) 5 years when they decide to remove that option?

You obviously didn't read TFA either - or even the Slashdot summary.

Four options are giving to manufacturers, with the last option being:

"or a speed control function in which the speed of the vehicle will be gradually reduced."

That sounds rather like "speed limiting" to me, does it not?

Not in the UK you wouldn't - with ambulance response times at a record low.