If you distribute Linux crackers then you need to provide not just the list of ingredients but also the recipe used to make them.
If you distribute Linux crackers then you need to provide not just the list of ingredients but also the recipe used to make them.
How the OOM Killer asks a process to terminate:
indiscriminate spraying
Thanks! I was racking my brain trying to think of where I knew it from, and after seeing the page that you linked I’m almost certain that it’s After Burner that is causing my brain to trigger the 80s association.
You can tell just from the font that this book is from the 80s
But website ads don’t get the ad money like YouTube.
Their website doesn’t even have ads
I think for now Forgejo is a drop-in replacement. However since they are a hard-fork, at some point in the future they will diverge enough to be mutually incompatible, so the clock is ticking on migrating.
This is huge news. Great work to the contributors involved in making this happen.
Pi Zero is a completely different product class. Pico is a microcontroller. Pi and Pi Zero are single board computers.
deleted by creator
ITT: Rust programmers rewriting the joke in Rust.
If you’re not storing on a filesystem that calculates and checks erasure codes then you can always generate PAR2 files yourself.
deleted by creator
What was your XMPP client connecting to? Was it a well-known public endpoint (that they could be whitelisting) or was it a private server? If the latter then that indicates that they are allowing arbitrary IP connections which in theory means that you should be able to proxy any traffic you want. I doubt they are doing DPI, since TLS makes this very difficult these days when you don’t control the certificate stores on the clients.
I’d imagine they’re relying on some combination of DNS whitelisting and port blocking which should be trivial to circumvent if you know ahead of time what traffic they allow through.
😱 ⛔🚫🙅🛑✋❌☠️
It sounds like they have some nice improvements, but I wonder why they didn’t contribute them back to the original restic project.
I also wouldn’t rely on an immature piece of software to handle backups - you want to avoid as many risk factors as possible with backups, since when you need to restore you really need it to work.
Thanks for posting this. I’ve been meaning to write something similar for a while but never got around to it. I wish Restic would ship an official client application for managing this stuff!
I like to pipe my json to
python -m json.tool
for quick formatting in the terminal.