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!
Recall for Linux
91–100 of 228 posts
Re: Recall for Linux
#92Its 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://github.com/jasonjmcghee/rem ?
Here's the Show HN: https://news.ycombinator.com/item?id=38787892
Re: Recall for Linux
#93needs more AI! also y no rust?
Re: Recall for Linux
#94Earlier quoted context omitted.
> Even apps that could easily be built into a single binary use these odd installation methods. Yeah because the curl bash script can deal with automatically selecting the right binary (even on Mac) and adding it to your PATH. > And while Flatpak gets a lot of criticism, I honestly think it's far better than these `script| bash` methods. I agree but does Flatpak actually work for CLI tools (which is where I see most…
> I agree but does Flatpak actually work for CLI tools (which is where I see most use of curl-bash). E.g. could I install Rust using Flatpak? My understanding was it's more suited for sandboxed GUI apps. Distrobox is basically flatpak for CLI apps. Not exactly, but it accomplishes a similar goal.
Doesn't it use Docker? Fine for trying stuff out on different distros but there's no way I want Docker as a normal installation process.
Docker is what you use if you've failed to do it the right way.
Re: Recall for Linux
#95For the first time since the 1980's I'm not going to be running a PC with a Microsoft OS on anywhere (I dual boot my main desktop since I use it for work and gaming) but the Windows 11 install is getting binned. Tired of having to read release notes carefully and make sure I've done just the right things to stop it doing things I never asked it to do. Good job MS, you lost a customer who's never likely to come back.…
> but the Windows 11 install is getting binned That makes you the best MS customer: you paid and you are not costing them anything in support.
For now. That all changes when the OP buys another computer.
There are plenty of vendors who will give you a OS less device and even a Linux device.
Re: Recall for Linux
#96Earlier quoted context omitted.
> Even apps that could easily be built into a single binary use these odd installation methods. Yeah because the curl bash script can deal with automatically selecting the right binary (even on Mac) and adding it to your PATH. > And while Flatpak gets a lot of criticism, I honestly think it's far better than these `script| bash` methods. I agree but does Flatpak actually work for CLI tools (which is where I see most…
No. It is absolutely ridiculous to suggest that one must read some unknown script just for the simple task of adding a binary to the directory on PATH. Unless, of course, you're the type of person who just runs any script without verification. Furthermore, for files installed 'automatically' like that, it's nearly impossible to remember what was done and where. This means that to remove it, you have to find and read…
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.
Re: Recall for Linux
#97Earlier quoted context omitted.
To me it felt like just shoving more AI for the sake of it, pretending that there is a problem to solve while making no case for it, and boiling oceans along the way as an acceptable externality.
Recall is an attempt at a solution all of us have encountered so many times in life.
Taking screenshots of your whole desktop every other second and sending it to a third part, just in case their OCR and cheap search built on top of it might come up with something useful? I haven't found a single situation where I would rather take that above more conventional and established approaches (browser history search, bookmarking, file management hygiene, etc)
Re: Recall for Linux
#98Earlier quoted context omitted.
> ...outside of gaming my computing life is linux... If you've games purchased through Steam, try running them on Linux with the officially-supported-and-written-for-Linux Steam client. Over the past decade+, a ton of work has been put into making games work fine under Wine and Valve's fork of Wine called Proton. I've found that nearly every game in my embarrassingly-large Steam library works fine on Linux.
> I've found that nearly every game in my embarrassingly-large Steam library works fine on Linux. I have on occasion been scared off of buying a package from Humble Bundle when the games are available on Steam but not explicitly marked as linux. (Some of the games are marked with linux and some are not.) Are you saying I am being unnecessarily cautious? For example, there is a "momcore" bundle at the moment where som…
> Are you saying I am being unnecessarily cautious?
Yes.
If a game is marked with Linux, that means it has a native Linux port. However, Proton has gotten so good in recent years that some of the native Linux ports actually perform _worse_ than just downloading the Windows exe and running it with the compatibility layer.
The investment in Proton makes sense in retrospect, since SteamOS is based on Arch Linux, and most of these games you mention should run just fine on a Steam Deck.
Re: Recall for Linux
#99Earlier quoted context omitted.
The value MS gains from milking to non technical people for all they’re worth outweighs the loss of the occasional tech savvy user. And sadly I think MS are still far from the tipping point and it will get worse and worse for some time to come. The only thing the non-techies have is the law to protect them.
I've directly moved at least 3 people out of Windows, and indirectly I'd guess at least a dozen. If all of us techies did the same, it'd be over pretty soon.
I've no one left to convert, my mums been running Linux since ~2016 when I got tired of her breaking windows (and in fairness it was her doing it most of the time) so I switched her to mint.
Her only requirement for her new computer is "it has to run that minty thing?" (it's actually running Fedora and has been for quite a while but that's the nice thing - she doesn't need to know or care) - it's still the same for her either way.
Re: Recall for Linux
#100Earlier 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
But somehow the malware infested/backdoored alternative has more appeal? Even more than the myriad of other distros, or DIY options for that matter? Doesn't click.
> myriad of other distros, or DIY options for that matter
Have you ever seen a working configuration? The only other distro that advertises it out of the box is Fedora. And maybe it is better in this respect than Ubuntu, but I already wasted a few days dealing with the fallout, so maybe I'll try it next year.
Manual - maybe. But is spending time learning yet another distro worth the Windows license?
re: malware/backdoored
I am not running self-wafered CPU, so backdoors at certain levels are outside of the threat model.
If anything, Ubuntu was "malware" in the sense that it didn't work as advertised. https://documentation.ubuntu.com/core/how-to-guides/manage-u...
> After entering a valid key, Ubuntu Core will decrypt the device, proceed with the boot, and restore the TPM from the recovered key. The recovery keys will remain the same and do not need to be retrieved again.
The restore TPM bit just didn't happen.