Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> In truth ( so far ) .. you can opt out (not easily) and here Microsoft is guilty of poor engineering rather than active hostility (although hard to seperate).

I find that a bit hard to believe given how aggressive Microsoft is putting copilot in the market. Copilot buttons on keyboards, in edge, in the windows toolbar, all without being asked for it.

I think it's more of a combo of both elements. I'm sure the marketing people don't like it being too easily removable. And the "not easy" opt out process is something I already call user hostile for such an invasive feature.

Sure it's only on copilot+ hardware but soon that'll be the only thing one can buy. And there's more reasons to want local AI without having a big brother spyware integrated.



Chris Titus is skeptical and has a community of windows hackers and former (and likely current) Microsoft engineers commenting on his work and offering tips.

_So far_ to date it's plausible to see what's happened with Recall being hard to "safely" remove as casual incompetence rather than deliberate malicious behaviour.

He expands on this in the latter part of the video linked above - but a very good point is that moving into the future, whether intended or not, care will likely not be taken to ensure ease of removal and seamless operation after scapel applied simply because the Windows stack of cards is getting big, unwieldy, and harder and herder for single engineers to grasp all of.

> And the "not easy" opt out process

In this specific instance it looks more like human error on a dependancy tree .. generally these are correct in Microsoft packages, screwups can happen.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: