How'd you do that? I've made registry tweaks, group policy tweaks, etc and my windows machine still eventually hits a limit where it forces updates around the 12 week mark. Granted it's still longer than before, it isn't completely disabled.

Linux activists deficiently root against Windows

Have you seen Linux users whenever anything controversial happens? Like rust in the kernel, C devs being jerks, Wayland, Pipewire, Flatpaks, or tbh anything else that causes Linux users to loose their minds?

Nobody acturally expects privacy from Apple, if you use an Apple device they know Apple has all your information.

Oh, they love to chew each other up.

But, you know, it's in that left-of-centre, obnoxious-software-engineer way where they all think they have the right answer to whatever the issue is, they're going to save the world and make Linux the One OS and everybody else is an idiot. That doesn't count.

You may want to have a conversation with Nobody, I don't think he got the memo.

Regardless, the point is Apple gets more of a pass. If I say "nobody actually expects privacy from Microsoft" that's undeniably true, but hardly works as an excuse, does it?

At that point it's easier to install Linux.

I run Linux too, but I have to use windows for some contract jobs.

Sure but Windows users are far more likely to demand privacy while Apple users just accept thats not a thing on Apple.

Well you see my distribution of choice is the perfect choice, my window manager is the best one, and my specific choice of utilies (ex: Terminal, shell, text editor, file manager, toolkit, etc) are the best ones. Clearly you're the one trying to divide Linux users :3

(And of course my standard is the best one, yes there are thirty other universal standards but mine is better)

around the 12 week mark.

Not all computers need to tell the date & time, just uninstall clock.exe

It was a combination of things between policies and taking over folder and file permissions. I can look up the specifics I used if you are looking to replicate it. It's a bitch to undo unless you write down everything you change.

In what sense?

Programs ran through Flatpak can only access permissions and directories that it has explicit permission for. This is perfect for a very small program that only does one thing, it can get rather awkward when you need it to access multiple storage volumes. For example, I wanted to have my Steam games stored on different hard drives, but they were never visible through Steam. I had to override the Flatpak permission to give access to my mounted disks for it to work.

I've disabled Windows completely so I can be safe and sound. Never going to put that shit on my PC.

-- sorry, it seemed funnier in my head.

Don't worry, Microsoft is bringing semantic search to Windows too. That way you can have the worst of both worlds.

• if you send plaintext, their email service could spy on them
• once they decrypt, they could accidentally reply with the decryped text, or it could get backed up if they store a copy somewhere
• screen readers could store decrypted email

In general, if you don't trust the receiver, you shouldn't send sensitive information. Windows Recall doesn't change that, if they're competent, Windows Recall won't be enabled.

I think this is more an issue for less technical users instead of activists, because activists will be more careful about who they trust than a secretary or something for a powerful individual.

Access controls is the big difference. Apps with sensitive data can choose to hide stuff to a system wid search API. It can do so on an individual level, even. And even if it previously was accessible it can be drumroll recalled. Exposure happens when a search is made.

Microsoft Recall is all or nothing. Once it has been displayed Recall has it and you can't selectively erase stuff. Exposure is immediate. It's just purge the whole database, or leave it all in there. Apps can't retroactively flag stuff.

... But leaving AI summaries on by default was very stupid by Apple

I'd argue that this is way more nuance than the public in general puts into the issue. In fact, the goalposts have moved quite a bit. "The big difference" used to be the local encription of the data, but it became not it once Recall implemented that. Or the opt-in, which went the same way.

That's not to say I don't think it's a better idea to have per-app support (which is incidentally how Microsoft implemented the feature in Windows 8 the first time), but I will say that's not why people are mad at one and not the other.

I don't actually know if you can selectively erase specific screenshots from the database because I, again, can't find any traces of Recall on my supported PCs for the life of me. Coverage had made it seem that they could, since presumably the much criticised side effect of having a local, freely accessible database with just a bunch of pictures is that you could... you know, access those. Did they obscure it further in the reimplementation?

And also, I think people believe I'm being argumentative, but I'm not. Can somebody point me at the Recall opt-in and/or some explanation why my Copilot + device running 24H2 would not seem to have it available anywhere? I'm confused about the rollout here. I don't want it on, but I'd like to try it and see what the practical implementation is for myself (and be double sure I have it turned off once I'm done with that).

They used the invasion of privacy to destroy the invasion of privacy?

This is just a thinly veiled ad for AdGuard.