I just tried it on Nobara. Just… application launcher (The start menu icon)->sleep. Waited, and then woke the machine back up and when the machine came back up, the game was still running. No idea if all games will play nice with that, but Satisfactory did.
Adding even more grammar, you could use “Had no”, for lack of possession, like
It had no tooling for the fs?
Accounting details, sensitive credentials for sys admin use, HIPAA data, PII etc. there’s just so much crap understood to be temporarily unlocked, viewed, and then immediately deleted or locked again. Even home users shouldn’t turn this thing on, check your bank? Balance and account details now always available. Use a password manager? Whatever you looked at is likely captured.
Had something similar happen with indiegala. Had an account with them for years, then one day, could not purchase some games randomly. Hit up their support and got the answer “Oh, the purchase was denied because your account’s email address is detected as a temporary email address”… The email address I’ve been using on that account… for years… Is temporary.
Yay… Capitalism…
Nginx reverse proxy with keycloak for auth? There are a couple solutions for it, but here is one https://kevalnagda.github.io/configure-nginx-and-keycloak-to-enable-sso-for-proxied-applications
The short answer is Rust was built with safety in mind. The longer answer is C was built mostly to abstract from assembly without much thought to safety. In C, if you want to use an array, you must manually request a chunk of memory, check to make sure you are writing within the bounds of your array, and free up the memory used by your array when completely done using it. If you do not do those steps correctly, you could write to a null pointer, cause a buffer overflow error, a use-after-free error, or memory leak depending on what step was forgotten or done out of order. In Rust, the compiler keeps track of when variables are used through a borrowing system. With this borrowing system the Rust compiler requests and frees memory safely. It also checks array bounds at run-time without a programmer explicitly needing to code it in. Several high-level languages have alot of these safety features too. C# for example, can make sure objects are not freed until they fall out of scope, but it does this at run-time with a garbage collector where Rust borrower rules are done at compile-time.
Some of the projects that pushed my own learning were very small things to help my school or work. When I was younger I had to do 100 FOIL equations and show my work. I did not want to do that all by hand and wrote a program to do it. If you got something super repetitive but not super hard, that would be a perfect project.
Gimp is my go-to
I don’t think this is possible through DNS filtering because it is your home lemmy instance showing you the results. You could block specific communities, turn off NSFW posts in your profile, or use a filter in Ublock Origin. These are all client-side solutions and would not auto-apply to a whole network. I don’t think there is a feature to block posts from a whole instance without being in charge of your own instance and de-federating. I would wager a per-user instance block will be coming down the pipe eventually.
At least it appears to be something that gets triggered. In theory, if a node is not under attack or heavy usage, this isn’t a consideration. Doesn’t seem to be a perfect solution as it still slows the traffic of legitimate users in the event of an attack. I don’t know the full details, but in the worse case it makes it easier to semi-DoS, maybe not by fully making a node unresponsive, but by making the service so painfully slow that users may give up on it.