Blah blah blah blah blah blah, I’m going to ignore 30 years of MS being open about policy and handling oodles of data because it doesn’t align with what I want the policy to be.
Let’s say for the sake of argument that is does remain all local. Hogging up your CPU, RAM, and Disk space, but its all local, unlike every other bit telemetry.
If it is completely local, why would I want it? What does the end user gain? I can think of what non-Microsoft agents would gain. If your computer got compromised, now a third party can see everything Recall logged. Could be completely mundane, could be private information, could be something worth blackmailing someone other.
Today I had to punch in my SSN and phone number to for my health insurance to confirm who I said I am. I don’t want anyone to know that who has no direct need to.
So if it is completely local, and everyone is opt-in by default, why would I want it in the first place? What does the end user gain? If I wanted my CPU hogged up for no reason, I’d start mining Bitcoin. If it was harmless, why is Microsoft not really commenting on it on the same way they do other things like Office, Teams, Xbox, etc.
Don’t care about the ram or CPU I don’t have performance issues and I could not care less that I might be in theory 1.5 fps. If performance is a concern, turn it off.
As for what I’d use it for, global transcriptions, better search, per page search in documents, local searchable documentation, summarization of long contacts, etc. if that’s not useful, turn it off.
As for security, this is nothing worse than a locally cached session. If someone already has os level read and write your already fucked. Same with bitwarden or any other app storing credentials. At the end of the day is written to disk. If you don’t like that turn it off.
Don’t care about the ram or CPU I don’t have performance issues and I could not care less that I might be in theory 1.5 fps. If performance is a concern, turn it off.
you would be surprised what using a lighter OS would do for your system responsiveness. Your system will boot faster, become usable quicker, launch applications sooner, and use less ram. All of which is for free.
Tell me you are desperately searching Google for ammo without saying a word.
The links there have nothing to do with changing policy or not being upfront. The children thing is about MS missing alerts to parents over changes to specific property charges. It’s not like they didn’t even have alerts, just not for these properties. Real fucking evil right?
All of these legal challenge are on the implementation not MS lying to you in the ToS. They used both of these services as documentated.
So again, show me a case where MS lied about what is collected and not this desperate unrelated bullshit. MS isn’t lying about how they are using your data.
Also: Even when stuff is written in the ToS it can still be illegal. (According to European law)
Microsoft has broken GDPR laws in the past and will continue to do so. Whether it is written in the ToS or not.
(PS: I am not using the data hog google either)
(PS: it is called “researching”. Not " desperately searching for ammo")
It’s pretty clear most of you can’t be bothered to read past headlines.
Recall is local and they aren’t using your data for upstream training.
“RecAlL Is loCal TheY” not gonna try to find out and im not trusting for sht anyways until independant network traffic analysis
Blah blah blah blah blah blah, I’m going to ignore 30 years of MS being open about policy and handling oodles of data because it doesn’t align with what I want the policy to be.
Just as dumb as the Alexa is spying on us crowd.
Let’s say for the sake of argument that is does remain all local. Hogging up your CPU, RAM, and Disk space, but its all local, unlike every other bit telemetry.
If it is completely local, why would I want it? What does the end user gain? I can think of what non-Microsoft agents would gain. If your computer got compromised, now a third party can see everything Recall logged. Could be completely mundane, could be private information, could be something worth blackmailing someone other.
Today I had to punch in my SSN and phone number to for my health insurance to confirm who I said I am. I don’t want anyone to know that who has no direct need to.
So if it is completely local, and everyone is opt-in by default, why would I want it in the first place? What does the end user gain? If I wanted my CPU hogged up for no reason, I’d start mining Bitcoin. If it was harmless, why is Microsoft not really commenting on it on the same way they do other things like Office, Teams, Xbox, etc.
Don’t care about the ram or CPU I don’t have performance issues and I could not care less that I might be in theory 1.5 fps. If performance is a concern, turn it off.
As for what I’d use it for, global transcriptions, better search, per page search in documents, local searchable documentation, summarization of long contacts, etc. if that’s not useful, turn it off.
As for security, this is nothing worse than a locally cached session. If someone already has os level read and write your already fucked. Same with bitwarden or any other app storing credentials. At the end of the day is written to disk. If you don’t like that turn it off.
you would be surprised what using a lighter OS would do for your system responsiveness. Your system will boot faster, become usable quicker, launch applications sooner, and use less ram. All of which is for free.
right 30 years of selling user data an enshittification and the home assistants from a companny that regularly pays fines for privacy infringement
Please point out a single instance where Microsoft was fined not using the data in the way described in the terms of service.
https://www.ftc.gov/news-events/news/press-releases/2023/06/ftc-will-require-microsoft-pay-20-million-over-charges-it-illegally-collected-personal-information
https://www.cnil.fr/en/cookies-microsoft-ireland-operations-limited-fined-60-million-euros
https://www.windowscentral.com/microsoft/microsoft-expects-to-pay-dollar425-million-fine-for-linkedin-privacy-violations
And then there are the cases where European institutions got sued for USING Microsoft products.
Tell me you are desperately searching Google for ammo without saying a word.
The links there have nothing to do with changing policy or not being upfront. The children thing is about MS missing alerts to parents over changes to specific property charges. It’s not like they didn’t even have alerts, just not for these properties. Real fucking evil right?
All of these legal challenge are on the implementation not MS lying to you in the ToS. They used both of these services as documentated.
So again, show me a case where MS lied about what is collected and not this desperate unrelated bullshit. MS isn’t lying about how they are using your data.
Oh boy. Do I need to crack open the case from 2018 where a Dutch team found out that Microsoft was collecting data WITHOUT stating it in the ToS.
https://www.theregister.com/2018/11/16/microsoft_gdpr
Also: Even when stuff is written in the ToS it can still be illegal. (According to European law) Microsoft has broken GDPR laws in the past and will continue to do so. Whether it is written in the ToS or not.
(PS: I am not using the data hog google either) (PS: it is called “researching”. Not " desperately searching for ammo")
Let’s see if the Microsoft bootlicker has an argument other than “Oh but that was in the past, who’s to say it’s still happening?”