yeah silly me for supporting artists with my money but also downloading drm-free copies of things so I can actually exercise a semblance of ownership. but sure, keelhaul me so you can keep your sense of smug superiority.
yeah silly me for supporting artists with my money but also downloading drm-free copies of things so I can actually exercise a semblance of ownership. but sure, keelhaul me so you can keep your sense of smug superiority.
AI is a tool that is fundamentally based on the concept of theft and plagiarism. The LLM training data comes from artists and creators that did not consent to their work being plagiarized by a hallucinating machine.
i would argue that leftists constantly arguing about what their words even mean is one of the biggest turn offs.
people don’t love pedantry.
faster can still lead to battery life improvements. if the CPU is able to complete tasks in less time, it can then enter a lower power state sooner which will result in less battery usage overall
assuming you have a GNU toolchain you can use the find
command like so:
find . -type f -executable -exec sh -c '
case $( file "$1" ) in (*Bourne-Again*) exit 0; esac
exit 1' sh {} \; -print0 | xargs -0 -I{} cp {} target/
This first finds all executable files in the current directory (change the “.” arg in find to search other dirs), uses the file
command to test if it’s a bash file, and if it is, pipes the file name to xargs
which calls cp
on each file.
note: if “target” is inside the search directory you’ll get output from cp
that it skipped copying identical files. this is because find
will find them a free you copy them so be careful!
note 2: this doesn’t preserve the directory structure of the files, so if your scripts are nested and might have duplicate names, you’ll get errors.
why use docker here? you’re just adding layers of abstraction in an environment that can’t seem to really support them.
that said, switching to 32bit linux, if the VPS supports it, will save you memory.
a surprisingly disappointing article from ars, i expect better from them.
the author appears to be confusing “relay attacks” with “cloning” and doesn’t really explain the flow of the attach that well.
really this just sounds like a complicated MitM attack, using the victim’s phone as the “middle” component between the victim’s physical card and the attacker’s rooted phone.
the whole “cloning the UID attack” at the end of the article is irrelevant, NFC payment cards don’t work like that.