![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
For completeness, we should review the involuntarily uploaded data as well.
For completeness, we should review the involuntarily uploaded data as well.
You’re not the boss of me now!
You could also run a shell command that kills vim from within vim… :!killall -9 vim
.
I don’t know, Schlitz beer is doing okay
Am moron, but I think you should trust melon on the internet
Agreed. This meme is in media res.
I don’t mean to sound all new agey, but I feel like we’re disrespecting the planet by dyeing a freakin river.
I don’t? You can apply a similar technique to bust file hashes. Add a new comment to each source file, or whatever.
My point is that automated methods to detect unwanted content will only get GitHub so far. It will have to be fuzzy, and that means it’s an arms race between detectors and obfuscators.
It would be possible to create a dummy “salt” commit and rebase every the branch onto it. The content would effectively be the same, but each commit hash would differ.
Wow, that is an unhelpful error message. It could have told you it was expecting a number. It turns out that -i
is short for “interval” and expects a number, whereas -I
is used to specify an interface.
Below you will find my highly researched list of advantages over the typical smartphone:
Meanwhile, ChromeOS 120 is off the scale
sudo chown -R $USER:$USER /usr/lib
It’s a tool. It’s useful to figure out if something you’re running is IO-bound or CPU-bound. It also shows per-core load, which is useful for visualizing multi-threaded performance.
That’s what pkill is for.
Sure, but if humans evolved from monkeys, how come there are still monkeys?
DRM = Direct Rendering Manager, in case anyone else was thinking Digital Rights Management…
https://en.wikipedia.org/wiki/Direct_Rendering_Manager