One rule of thumb is `mv` will keep the attributes by default (given similar filesystem) and everything else needs tweaking/extra args. There's a section on it over here:
https://wiki.archlinux.org/title/Extended_attributes#Preserv...
One rule of thumb is `mv` will keep the attributes by default (given similar filesystem) and everything else needs tweaking/extra args. There's a section on it over here:
https://wiki.archlinux.org/title/Extended_attributes#Preserv...
Not literally, but this was the thesis of your comment, regardless of your four words of validation.
> I admit it is perhaps unkind of me to not provide the laundry list of AI-tells in their article
Please don't do this. It doesn't matter.
> what explanation do I owe them?
What explanation do they owe you?
> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
Just pretend "this is AI slop" is also in the list. Don't complain about that; complain about the information being wrong or something else insightful. Discuss the conclusions that were included in the article. Assume (also per the guidelines) that the author reviewed the article before posting; they are signing off on its validity and therefore any callouts, AI-related or otherwise, should be calling that validity into question rather than simply saying that a particular tool was used for getting the words on the page.
I admit it is perhaps unkind of me to not provide the laundry list of AI-tells in their article, but I see their response to me as being a direct lie ("I haven't used AI to write this post, that's just my style") so what explanation do I owe them?
Dead Comment
The system call to read these attributes is getxattr(), for anyone curious.
Eg: one could piggy-back an entirely new file onto an existing file (it might have to be text encoded?).
It looks like the kernel might impose a limit of 64KiB on a file's metadata, but that's still quite a lot of room for data smuggling...