"Recall uses Copilot+ PC advanced processing capabilities to take images of your active screen every few seconds,"
Seems like a lot of extra disk thrashing that would shorten the life expectancy of an SSD? Like it would be considerably more than your usual background chatter of daemons writing to log files and what not. Unless I'm misunderstanding this?
I live in the path of totality and the local tourism office is projecting anywhere from 70K to half a million visitors. It's insane! Also, I read Niagara Falls, which is obviously used to seeing a lot of tourists, has nevertheless declared a preemptive state of emergency. And there are advisories to be very careful if you're driving on highways at the time of totality, as there will inevitably be idiots who stop suddenly to gawk and burn out their eyeballs.
Mind you, it could all be a bust given the current weather forecast is for Monday to be cloudy across the whole region. I guess it'll still be cool to see everything go dark for a few minutes though.
I have some vague recollection of a hacker convention from the 90s where people were challenged to come up with wireless networking in a one night coding marathon. (This was long before wifi.) So some dude used speech synthesis to get a machine to say "one zero one one zero…" and another to assemble the binary data into packets using speech recognition. It was hilarious, and the dev had to keep telling people to shut up and stop laughing so he could complete the demo.
But anyways… what I'm trying to suggest here is you might have the best luck if your notification sounds contain spoken commands and you use speech recognition to trigger scripts? That tech is pretty mature at this point.
There should be a law that whenever this happens, the changes must be highlighted in bold.
I was astonished to find the other day that LibreOffice has no problem opening ClarisWorks files. That is an ancient Mac format that even Apple's Pages has long since abandoned.
Oh yeah, that's another way to make a subshell. But don't forget to stick the find in there also:
sudo sh -c 'cd ./testar && find . -maxdepth 1 -type d,f' | ...The commands within the parentheses run in a temporarily created subshell with its own environment. So you can change the working directory within it and it won't effect your main shell's working directory.
Let's say you're in the home directory that's called /home/joe. You could go something like:
> (cd bin && pwd) && pwd
/home/joe/bin
/home/joe
If find had something equivalent to tar -C, you wouldn't need to do this, but I don't think it does?
Ok, I actually tried something like this at a terminal. You do still need the -C ./testar if you use the subshell since tar won't know where to look otherwise.
(sudo cd ./testar && sudo find . -maxdepth 1 -type d,f) | sudo tar -czvf ./xtractar/tar2/testbackup2.tgz -C ./testar -T -
This will still give you a listing with ./text.tz and so on because find prints ./whatever when you search .. I think this is harmless? But I suppose you could remove them if it bothers you.
(sudo cd ./testar && sudo find . -maxdepth 1 -type d,f) | cut -c3- | sudo tar -czvf ./xtractar/tar2/testbackup2.tgz -C ./testar -T -I think that since you're piping in the file list from find, the -C ./testar in the tar command is basically irrelevant? You probably need to cd ./testar before the find. Maybe you could do that in a subshell so that the cd doesn't affect your tar archive path? So something like:
(sudo cd ./testar && sudo find ./ -maxdepth 1 -type d,f) | sudo tar -czvf ./xtractar/tar2/testbackup2.tgz -T -
Good Lord, if the US nuclear arsenal is that antiquated, I shudder to think of where the Russians are at. Please don't short-circuit and accidentally launch…
At least it appears to be available in Canada now…
So the next captcha will be a list of AI-generated statements and you have to decide which are bat shit crazy?