Earlier quoted context omitted.
I think you hit the nail on the head. Recall was problematic because of the lack of information provided when they announced it. How would it handle sensitive details like banking account pages. Can developers opt out for best security practices? How is the managed in an enterprise environment? Once they delayed and got all their ducks in a row it's a much more solid feature. Not for everyone, but a good way to lever…
What irritates me most about all these unwanted "innovations" is that they always make them opt-out. "If it's opt-in, nobody's gonna use it - and it's such a flawless feature, we should be shoving it down everyone's throats"
Recall for Linux
201–210 of 228 posts
Re: Recall for Linux
#202Earlier quoted context omitted.
Love bazzite on my 9070/9800x3d setup. Zero issues with a game yet. Played expedition 33 the day I built it a few months back!
Nice, I'm running a 7900XTX/7950X3D so I may give it a try - I don't game anything like as much as I used to though anyway so if the odd game did cause issues it's no biggie.
Re: Recall for Linux
#203Earlier quoted context omitted.
I just nuked my home server Ubuntu and installed Windows. Canonical is still unable to make reliable TPM-unlocked full disk encryption, unacceptable for me as a data hoarder. https://bugs.launchpad.net/snapd/+bug/2045417
This is something that's bugged me about BitLocker for ages: What's the point of encrypting your disks if the computer automatically decrypts them anyway? The only situation I can see where this helps you is if someone steals your disk but not your computer, but that seems very unlikely to me. Maybe if someone just clones the disk, but again, it seems much more likely to me that if you're a high enough value target t…
Your security. We also back up your key in the cloud, in case you forget it. /s
Re: Recall for Linux
#204I was expecting OneDrive subscription message to go up from time time time.
Re: Recall for Linux
#205Earlier quoted context omitted.
Yeah uninstallation is a flaw, but what alternative are you suggesting? And yes I am the type of person that uses heuristics to trust what software to run. You aren't magically safer if you audit the install script and not the actual binary.
The smaller the attack surface, the better. There is no need to expand it unnecessarily. By your logic, we shouldn't even use the binaries provided by the official package manager, because they also cannot be trusted. We are talking about the dangers of the installation method. Not the program itself.
It only makes sense to separate them if you install the program and then never run it which is obviously ridiculous.
> There is no need to expand it unnecessarily.
I agree, but it is necessary because there aren't any good alternatives.
Also it is very minimal additional risk. If it wasn't we'd see it used as an attack method and as far as I know that has yet to happen once.
Re: Recall for Linux
#206Earlier quoted context omitted.
It has been over a decade that big tech has been playing this script: * Introduce a feature that is abysmal for user privacy * Promise it's okay because $reasons * Make the feature opt-out * Change the EULA so that $reasons are no longer applicable/valid * Roll out an update that "accidentally" turns the feature back on for everyone * Apologize, deny, divert, deflect * Siphon off all that sweet sweet user data Rinse…
You are merely objecting to Microsoft being the developer behind Recall. Great I don't fault you for that. But now consider hypothetically what if the Linux Foundation developed and announced Recall?
They are not known for siphoning user data through dark patterns, so there is nothing to object from me. If they were to try it the same underhanded way as microsoft, I'd be just as much against it.
Re: Recall for Linux
#207LOL, can’t believe a Linux app turned out to be an .exe file.
To be more "native" shall have the extension com or lnk.
Re: Recall for Linux
#208I never understood the hate for Recall. The idea is definitely good. In fact I want this sort of feature to work across my devices. I guess people don't trust Microsoft to implement it in a secure way?
It is like making sex with all your coleagues and your boss watching you and getting a performance review based on this.
Re: Recall for Linux
#209Earlier quoted context omitted.
You are merely objecting to Microsoft being the developer behind Recall. Great I don't fault you for that. But now consider hypothetically what if the Linux Foundation developed and announced Recall?
The linux foundation would introduce this is an optional thing you can download, with documentation on how it works, and where you can find the source. Within 3 days the community would make self hosted servers for it. They are not known for siphoning user data through dark patterns, so there is nothing to object from me. If they were to try it the same underhanded way as microsoft, I'd be just as much against it.
Re: Recall for Linux
#210From the installation instructions; curl -fsSL https://tinyurl.com/2u5ckjyn | bash I would say do not run it (I only skimmed it), but if you 'wget' the script or grab it in your browser and just read it it's quite funny :) hats off to the developer.
You can read the script in the repo: https://github.com/rolflobker/recall-for-linux/blob/main/rec... (Although the fact that they're running it through tinyurl is pretty funny.)