The problem with this argument, from the shop's point of view, is that the UK is in the middle of a shoplifting epidemic. The policing resources simply aren't there to deal with small scale (or even flagrant and much larger scale) shoplifting. It now seems to be rare for police officers to attend reports of shoplifting at all. And so effectively shoplifting becomes legalised, which is obviously hurting the big chain stores financially and potentially devastating for smaller shops.

Shops are trying to find some way to respond to this to protect themselves. They typically tell staff, even security staff, not to get physical with shoplifters as they walk out, not least because the risk of something worse happening and the business becoming liable for it is significant. But then the shoplifters know this and some of them will just walk in and openly empty a shelf into a bag and walk out again without paying because they know no-one will try to stop them.

Shops also know that our court system is completely overwhelmed at the moment and there is little chance of bringing any successful civil action to recover damages from shoplifters who aren't even being arrested by the police and put through the criminal justice system.

So what do they have left? Basically, they're trying to spot the "usual suspects" and refuse them entry in the first place, which is a less risky proposition in terms of potential for physical violence and quite effective because a lot of shoplifting is done by the same people, or they're trying to make it more physically difficult to steal goods, for example by using locking systems or keeping high value items behind counters where customers can't just pick them up. But these systems aren't perfect, far from it, and what we're discussing here today is one of the significant problems.

Obviously this kind of technology can have very bad consequences, as we see here. I don't think it should be used if it's not highly reliable, given the potential harm done in cases where it gets something wrong. But I do have some sympathy with the shops who are looking for something -- anything -- to reduce the threat they're facing because the rule of law has failed in retail settings.

For me the visualization of direct collapse black hole formation is that there's still a huge mass of gas falling in, at the boundary of the new black hole nearly dense enough to direct collapse itself. The blowback would compress the inflow over the density edge and you get a whole cloud of black holes.

It's pretty cool that they're seeing where the supermassive black holes come from. The models of what's happening in there must be amazing.

On the contrary, I think most of your comment is as relevant as ever. A carefully designed UI is still better for almost any specific task than what "agents" will produce. It will probably be more efficient to describe what you want precisely enough to get it right. It will not be undermined by problems like non-repeatability, non-determinism and hallucinations that are inherent in LLM-backed agents.

Agents can be quite effective at getting something that seems about right, as long as you don't care too much about the details. And of course they get there much quicker than doing it manually as a human. This is useful for some tasks, and why they have become popular.

Unfortunately, it turns out that for many of the things we really care about, "about right" doesn't cut it. Right now, today, the software industry is already being overwhelmed by AI slop. It's hard to believe, but it's still only been a few months since agentic development processes arrived on the scene. And yet after just those few months of management trying to replace real developers with agents, we can see the slow-motion train wreck happening right before our eyes. And in return, where are the new applications that radically improve on what we had before thanks to all this added "productivity"? If this tech is going to change the world as the AI tech bros and the sycophantic CxOs kneeling at their feet would have us believe, where's my flying car?

Imagine a Beowulf cluster of AI-generated cybersecurity nightmares...

Whether we like it or not, whether we use Windows or not, Microsoft is going to insist on adding the tax whether the PC comes shipped with Windows or not. This is illegal bundling, Microsoft has essentially ignored prior rulings, and it's pretty much a certainty the courts will be fine with this.

It is. The fact that our dominant desktop operating systems are still using security models from last century is probably the #2 disaster of modern tech security, coming in just behind so much software with potential security implications still being written in languages like C and C++ at #1. And the understandable yet still deeply regrettable reason for both disasters is the same: momentum.

I normally connect to all online conference calls via their web UIs. At least then it takes both a screw-up in the communications system and a screw-up in a browser security sandbox that is independently developed to allow something like an RCE or data leakage vulnerability to be exploited.

People have called me crazy for not wanting to install native apps from the likes of Microsoft, Google and Zoom in the modern era of remote working, but every now and then, there's another story like this one that reminds me why I am extremely careful about what native software I install on anything these days.

What, specifically, do you mean by "personal Windows installations"?

Are you suggesting that any business of any size should only ever use Enterprise editions of Windows?

"How did you get hired?"
"I was top at Fortnite. You?"
"Combat flight sims."

"Damn, two Boeings just crashed over an oil refinery on city limits and took out half the city."
"Did you remember to save your position beforehand?"
"Yeah."
"The reload and continue from there. No-one will notice."

I love computer games. I have XPlane 12 and many scenery packs. I rank well on Elite:Dangerous. From the sounds of it, the FAA would see me as over-qualified. In reality? There's no way in hell I'd be taking those kinds of risks with real lives. There's a huge difference between having good reflexes and a good eye, versus having the complex 4D spacetime relationship mental models needed for robust air traffic control.

No, I read the details explicitly quoted at the start of the discussion and responded to them.

Are you saying that this episode has not in fact resulted in (a) unplanned software being installed on end devices that will (b) automatically read data that is stored on those devices without the proper approvals? Either of those things alone can easily become a compliance problem if you operate in a regulated environment, whether or not things ultimately go any further on this occasion.

You see, Linus has embraced transhumanism and is testing out the new kernel as a supplementary brain function, using MOSIX to offload all of the irritable comment generation at yet more nonsense on the mailing list to an Elizabot that he has written specifically to do this. This saves his actual brain for real work.

AI is not currently capable of performing any meaningful conceptual abstraction, it is only capable of very basic mechanical abstraction. Abstraction is itself multi-dimensional. Nor is there any indication that AI could ever perform multi-dimensional abstraction or multi-dimensional decomposition. Precious few humans are capable of it either, but some can.

No, AI would need humans because the best system is not a pure system but a hybrid system, and that means transhumanism with AI operating as an additional brain function rather than as a replacement for a brain.

Tool calling is, yes, but the current approach to it is (a) overt not transparent to the user, (b) not designed for the purpose I've outlined, and (c) not remotely good enough for the AI to be able to manage data through such tools.

Yes, you can connect an AI to a PostgreSQL database. Whoopee. Not even close to an AI detecting via classifiers that some of the data is relational in nature, transparently setting up its own PostgreSQL database in response, and using that proactively as an additional way to examine the data. You would need to explicitly set up the constructs, explicitly set up the databases, explicitly tell it when, where, and how to use the database, and if that particular usage conflicted with a way the AI actually worked, the AI would not be able to use it effectively. That's not remotely close to what I'm talking about.

What I'm talking about is much, much deeper than that. AIs lose focus when there is too much information currently in the system. Absolutely nothing stops an AI from using a document database as a virtual memory in which it can page in and out conceptual spaces so that the focus on any given step of a problem concerns just the problem. Other than such a concept not existing yet, which is kind of a limiting factor. But you need to know what connects to what. The AI could use an ontology reasoner for that, or a relational database, or an external graph. But you cannot provide those tools and you cannot configure them, for the simple reason that the AI is the only entity with any detailed map of how the underlying neural net is connecting those ideas up.

The AI itself has to select the tools, has to configure the tools, has to do all the work. Which means YOU cannot use any sort of API. YOU should have no involvement in the underlying mechanisms needed for the internal NN housekeeping.

And that's your other error. You're assuming this is about user data. No. It's about housekeeping operations within the NN itself to maximise functionality, it has nothing to do with the user side of things at all. If the user was capable of setting up dynamically structured databases that mutated with each step of a decomposed analysis, you'd have done everything the AI would be doing and you wouldn't need the AI to begin with.

You cannot do this work, you cannot even assist in this work, it has to be dynamic and it has to be utterly invisible to the operator.

It was obnoxious enough when Microsoft started pushing this kind of unwanted "feature" on home users, then small businesses and professionals on Pro editions. There are real legal and regulatory concerns over this kind of change that businesses have to take seriously. If they've screwed up so badly that even their large corporate customers have been hit by the same thing and there isn't even a good way to undo the damage at the moment, this could lead to meaningful lawsuits from their customers and/or interventions by regulators.