←back to thread

290 points XzetaU8 | 2 comments | | HN request time: 0.62s | source
Show context
LooseMarmoset ◴[] No.44657920[source]
Who, exactly, is clamoring for Recall in the first place?

And who is to say that Microsoft will honor the toggle, “for analytic and performance metric” purposes?

EDIT: the rant above shouldn’t cast aspersions on Brave, good on them for trying.

replies(12): >>44657932 #>>44657950 #>>44657957 #>>44658098 #>>44658105 #>>44658244 #>>44658305 #>>44658423 #>>44659926 #>>44661338 #>>44663007 #>>44664092 #
firesteelrain ◴[] No.44657932[source]
It seems it enables Copilot to assist the user in finding things on their PC.

Somehow find . -iname has worked for years in Linux without AI

replies(2): >>44658055 #>>44658232 #
thombles ◴[] No.44658232[source]
At least on OneDrive for Android, a bizarre thing is that search is _not_ equivalent to find . -iname. It is able to find search terms in the _content_ of documents but not their filenames.
replies(1): >>44658275 #
Ballas ◴[] No.44658275[source]
Well, you can have the same functionality with find if you want it:

find -type f -exec grep -Hn "_content_" {} \;

replies(1): >>44658977 #
rovr138 ◴[] No.44658977[source]

  grep -RHn "_content_" .
replies(1): >>44659027 #
1. dotancohen ◴[] No.44659027[source]
Though I much prefer this solution, the GP solution is better when there are non-text documents in the directory tree. Find is nice and that you can narrow it down by file name or file extension, without relying on bash globs.
replies(1): >>44659309 #
2. rovr138 ◴[] No.44659309[source]
Yep

I just did it more tongue-in-cheek like the unneeded cat commands.

There’s definitely use cases. If you want to search for a keyword on the file name, that one’s great.