Live data from Hacker News

Recall for Linux

github.com

161–170 of 228 posts

Re: Recall for Linux

#161

Earlier quoted context omitted.

For all that it is satire, it is a lot more functional than you might realize at first glance. https://github.com/rolflobker/recall-for-linux/blob/e16382f0...

Judging from the code, I’m pretty sure this is generated by AI

[dead]

Re: Recall for Linux

#162
post #73

Earlier 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…

> What's the point of encrypting your disks if the computer automatically decrypts them anyway?

The important detail you're missing is: the computer automatically decrypts your disks if you're booting into that operating system. Try booting into something else (like a Linux CD), and you'll see that the TPM does not release the encryption key (the way it works is that each step of the boot sequence records into the TPM what's going on, and the TPM will only release the key if the sequence matches what it expects).

The point is that the disks will only be decrypted when booting into the expected OS, and that this OS will require you to login before giving anyone access to your files.

> 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.

It'll also help if someone steals the computer but does not have your login password; they can boot into Windows, the files will be decrypted while booted into Windows, but without logging into your account, they are not accessible. Of course, unless you're using memory encryption (which I don't think is normally available on normal non-server devices), someone with the right hardware knowledge and an expensive set of hardware tools could in theory manipulate the RAM to get access.

Re: Recall for Linux

#163

Its kind of naive satire that looks silly on second thought. Recall was not bad because of the concept but implementation details, rollout communication and of course the microsoft part. Recall by an open entity with data ownership, security and transparency would have none of those issues and its just a new take on the universal desktop search that is enabled by ai being able to utilise pixels. I refuse to be shamed…

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 leverage your PC as a source of information that you can search without having to save everything.

The post reads a little childish to me. Very "Micro$hit are greedy and want to steal your data" level of criticism.

Re: Recall for Linux

#164
post #150

Earlier quoted context omitted.

I was very skeptical of the claim that gaming on linux is good now, but fully switched over last weekend. All of the games I play on a regular basis just worked out of the box with no fiddling at all (nVidia graphics card, X11, pop_OS - but I'm pretty sure any modern distribution would work just as well). Fresh OS install (nvidia drivers just worked), install the steam flatpack, click "download", click "play". That's…

Running steam itself as a flatpak may cost you between 10-15% in overhead if what I've read is true. Installing from repo on fedora/debian/etc should work in most cases just fine.

Oh really? Wow! I'll switch over tonight and give it a shot. Thanks!

Re: Recall for Linux

#165

Earlier quoted context omitted.

It does decrypt them. But then what? How are you the thief going to extract them or data from RAM of a working machine?

If it’s decrypted, you don’t need to steal it from RAM. You just do normal file operations and copy the files

you need to login to do that. The point of bitlocker is that it prevents filesystem access from a different OS install.

Re: Recall for Linux

#166

These recall apps disappoint me. They screenshot all the time. It's not enough data. They should be adding event driven window history reporting, accessibility tree scraping, and filesystem deltas too. I want a better exocortex!

Look up eidetic os - it runs a micro kernel and captures all the inputs to it, to be able to perfectly deterministicly replay everything. Like running all your programs under a time travel debugger.

It’s a cool idea I think!

Re: Recall for Linux

#167

I know this is satire, but there is actually one and one you actually control. May be useful to remember who said what and where. It can be useful. Just not the way a megacorp implements it. Here it is [unaffiliated, untested by me, unvetted]: https://github.com/openrecall/openrecall

This alternative is still storing the screenshots and the OCRed content unencrypted, and the web UI is also unauthenticated. There's some docs on storing the data in an encrypted volume or external drive, but 99% of people ain't doing that. The only real improvement over MS's version is keeping the data local, which ain't much, really.

> The only real improvement over MS's version is keeping the data local, which ain't much, really.

That's already a lot.

Re: Recall for Linux

#168
post #118

Earlier quoted context omitted.

It's bad in concept as well. All of that data sent to a third party server is going to be public on the Internet at some point . Security? Don't make me laugh. Countries that required government IDs to participate online have already made this mistake and those IDs have been leaked. Just because it's open source or run by $NOT_MICROSOFT won't make it any safer. The problem with other people consenting to it is that i…

Conceptually a feature similar to Recall doesn't have to involve sending any data to third parties. It should not need to be a service just a piece of software running locally, doing OCR and full text search indexing using local compute. Incidentally I often tell my friends I run an app on my phone that captures my location 24/7 and they would initially sound horrified. But then I tell them all my location data is no…

What location-tracking app do you use? How does it impact the battery life? That sounds useful.

Re: Recall for Linux

#169
post #129

Earlier quoted context omitted.

I'm pretty sure recall was specifically a selling point for laptops with ai chips which could do the processing locally and reasonably efficiently? Though storing the data locally still could make getting compromised by a targeted attack more dangerous.

I have to wonder what edge AI would look like on a laptop. Little super mini Nvidia Jetson? How much added cost? How much more weight for the second and third batteries? And the fourth and fifth batteries to be able to unplug for more than a few minutes?

It looks like a MacBook Pro and (maybe) a Snapdragon X2 device

Re: Recall for Linux

#170
post #85

Its kind of naive satire that looks silly on second thought. Recall was not bad because of the concept but implementation details, rollout communication and of course the microsoft part. Recall by an open entity with data ownership, security and transparency would have none of those issues and its just a new take on the universal desktop search that is enabled by ai being able to utilise pixels. I refuse to be shamed…

I still recall (duh) a post here from a guy who literally made a recall feature on his mac way before them. I would love to find that post... It was screenshotting all the time, storing that locally, and then you could ask it any questions and roll back to that moment. Processing was also fully local.

https://www.rewind.ai/
Post reply on HN