The fact that Microsoft's new Recall thing won't capture DRM content means the engineers do understand the risk of logging everything.
They just chose to preference the interests of corporates and money over people, deliberately.
Corporations of any significant size do not do anything substantial by accident. It is structurally impossible for them to do so.

In fact, research like this https://research-repository.uwa.edu.au/en/publications/catching-the-corporate-conscience-a-new-model-of-systems-intentio indicates that, legally, the purpose of a system is what it does.

"corporations manifest their intentions through the systems of conduct that they adopt and operate, both in the sense that any system reveals the corporate intention and in the sense that it embodies or instantiates that intention."

"Where there are patterns of misconduct, this will often reveal the presence of a system designed to, or apt to, produce that misconduct."

Catching the corporate conscience: a new model of “systems intentionality”

the UWA Profiles and Research Repository

@daedalus engineer here (not for this AI shit, obviously)

stuff like this is handed down from on high, trickling from C-levels, Product Managers, Project Managers, Engineering Managers, and finally landing in front of Engineers to implement. Microsoft is notorious in this style of management.

you can say "engineers are the ones who write the code so the buck stops with them," to which I say: why do you think Microsoft is so adamant about replacing them with robots? it's because engineers often push back on stuff like this and make things "difficult". it's Product that's always pushing these hare-brained schemes blindly because they want to meet OKR targets that engineers couldn't care less about.

@AmyZenunim @daedalus that doesn't exonerate the AI developers at Microsoft, it just makes them class traitors too.

@AmyZenunim @daedalus

Hard truth right here. It is exhausting.

"it's Product that's always pushing these hare-brained schemes blindly because they want to meet OKR targets that engineers couldn't care less about."

@daedalus “What about the COUS’?”

“Corporations Of Unusual Size? I don’t think they exist.”

@daedalus there’s no HDCP for personal information, only DRM’ed content, thanks to industry priorities.
@daedalus tbh it might be not sooo easy to capture DRMd content
@daedalus Question is… how do we make everything we do look like "DRM content" to the OS?
@daedalus Microsoft will care about home/end users when those people are responsible for the bulk of their revenue.

@daedalus Don't attribute to malice what can be explained by API limitations. It is far more likely that Microsoft isn't privileging their own app and isn't giving it any special access to Windows APIs that a third-party developer wouldn't have (which is a good thing). As a consequence, the app is just as unable to access "protected" content as any other third-party app. Look at Zoom, TeamViewer, or any other piece of remote access, teleconferencing, MDM or parental control software, and you will find the same limitation, regardless of which platform the software is running on. Notably, this also applies to open source software running on open operating systems.

Not giving this app access to DRMed content was just an easy technical decision to make.

@daedalus No, it literally can’t capture DRM content, because the DRM chain from decoder blob through hardware drivers to hardware is so tight. That’s the whole point of the DRM system for anything serious above 1080p.
@frumble @daedalus And they probably just use the normal Windows screenshot API, because it's well tested.
@daedalus @fennix say it louder for the people in the back

@daedalus As Raymond Chen @ Microsoft keeps saying, any new feature starts with negative 100 points.

Something this big starts with way fewer points than that because of the resource consumption - they're releasing it at 20% of the average disk size FFS.

@daedalus you sure are getting some real Replies to this huh
@daedalus Microsoft is not an engineer-driven company. Hasn't been since maybe the 90s.
@daedalus You cannot blame engineers or developers. It’s a total Microsoft issue.

@daedalus

Who owns the computer?

Who owns the computer?

@daedalus Well, they wanna Make sure they wont geht sued over what they sell. Customer data haven't got them in any trouble :P

@daedalus No it does not. The stuff is bad enough as it is, let's not add spurious wrong assertions to it.
DRM content has long been specially handled in the core. See for example https://en.wikipedia.org/wiki/Protected_Media_Path
It wouldn't be much of a DRM if you could just record the screen during playback.

Yes, you can probably circumvent that. And they would even be in a privileged position to do so.

But the point is, the most straightforward direct implementation *without thinking* doesn't capture DRM by default.

Protected Media Path - Wikipedia

@daedalus hey, why are you always running the matrix in a small window on your work computer, and why is the windows always on top

@daedalus For the most part, these are people also being crushed by capitalism boot.

While I'd argue some are likely willing/ignorant others are likely ignored, not trusted but used as a tool by management.

@daedalus nah, I don't think that's that. It's how DRM displaying implemented where it would render on monitor itself rather than in screen buffer, so when anything tries to make a screenshot, the area with DRM content simply displays black area. They just don't know how to work around that and decided they couldn't care less. Don't give them credit for that.
@daedalus my guess is that it just uses the usual screenshot apis for that and any drm content just renders as a black screen there anyway because it doesn't go through gdi/win32k to be rendered at all

https://eigenmagic.net/@daedalus/112481049072916563

So i guess any remotely sensitive app has to flag its UI as DRM'ed content then?

@daedalus

JP (@[email protected])

The fact that Microsoft's new Recall thing won't capture DRM content means the engineers do understand the risk of logging everything. They just chose to preference the interests of corporates and money over people, deliberately.

eigenmagic.net
@daedalus Didn't realize until today that Snipping Tool won't copy DRM Content. Just tried it out. Amazon Prime goes blank when I click on "New" in the Snipping Tool. But, if I have snipping tool running on my local PC and Prime running on a remote PC then bingo. DRM Bypass. Extrapolating, if I get a Copilot+ PC, my personal incognito window is protected. But any customer stuff I connect to is being slurped onto my PC. Some customers disable copy/paste in citrix. How will they feel about this?
@daedalus there needs to be a means to tell Recal, hold off on the snapshots for a mo, I'm about to show sensitive data.
@daedalus strange, I would have thought just taking occasional screen snapshots for rembeberign what you did would constitute fair use. of DRM content.
Not that I have any time for MS "Recall" AI as a concept: a complete waste of storage space, hardware and power.
@daedalus i would venture that "do understand" statement is more on product managers than the engineers implementing it

@daedalus

Can we copyright what is on our screen and wrap it in DRM?

@daedalus @leyrer what stops me from writing code that turns on DRM for my Putty and fully Browser sessions? 🤔
@daedalus More like they plugged into the same screenshare API with no thought at all, and that already blocks DRM content.