carid @[email protected]

Why does #Microsoft want to implement #Recall? It's not about *images*. It's about modelling what workers do on Windows, and then replacing them.

The most expensive part of a computer is the fallible feelings-filled unpredictable meat sack that operates it.

Google has YouTube, Google Photos, Maps, and a bucket load of search data, Google Analytics, advertising, as well as it's #GCP data (e.g. #STT transcriptions). And a bunch of data from Android services. From this data they can model speech, model videos and model advertising systems, and how humans respond to them.

But they can't model what people do on computers.

Amazon has Prime data, and a bucket load of compute. But no operating system data. They can build models based around e-commerce and advertising systems.

But they can't model what people do on computers.

Meta has *waves hands* enough analytics to model human behaviour in the Metaverse.

But they can't model what people do on computers.

Microsoft has GitHub.
Microsoft has LinkedIn.
Microsoft has SharePoint.
Microsoft has Teams.
Microsoft has Dynamics.
Microsoft has O365.
Microsoft has Windows telemetry data.

Microsoft can model what people do on (Windows) computers. Like fill out spreadsheets.Write emails. Synthesize web pages of research. Interact with colleagues on Teams. Create and edit documents.

Microsoft wants #MicrosoftRecall data so they can model what people *do* with operating systems.

Then replace them.

Imagine a CoPilot that doesn't just write buggy code. Imagine one that also does spreadsheets. That creates documents on SharePoint. That communicates with colleages on Teams. That has a customer pipeline on Dynamics.

That's what Recall is about - 360 degree surveillance of the worker, to model their functions, make them fungible, replicable - and replaceable.