can we go back?
No!
can we go back?
No!
I’d prefer GNU’s ddrescue just because I find it more robust and has better progress output. It’s functionally the same interface but lets you use a mapfile to resume sessions should anything happen to interrupt the copy.
Arguably I’m against this because you never know what’s going to happen and the conventional wisdom for appliances like this is to just backup any important configs, backup your containers and vms, then do a fresh install from the latest install media on the new disk followed by a restore of the backups. It might take a little more time but it’s negligible and allows you an opportunity to review your current configs, make necessary changes, and ensure your backups are working as intended.
Gran Turismo 4
Dirt Rally 2
Forza Horizons 4
And the godking itself, Burnout 4 Revenge and its understudy Burnout 3.
Bonus point to Extreme-G and G2.
I’m also going to mention Generally. It was a tiny game with a small dedicated community but gods damn if it wasn’t just super fun to make maps and play community created events/maps/contests.
According to this Blu-ray has some of the worst expected shelf life, with the exception of BD-RE.
Summer: $0.118 / kwh first 600kwh, $0.136 600+ Winter: $0.132 / kwh first 600kwh, $0.144 600+
I averaged the last 3 years for these.
I’ve literally thrown my back out trying to suppress sneezes. I gave up trying years ago, I’m a scream sneezer through and through. Dracula barely helps but at least it’s more sanitary.
In my experience, token limits mean nothing on larger context windows. 1 million tokens can easily be taken up by a very small amount of complex files. It also doesn’t do great traversing a tree to selectively find context which seems to be the most limiting factor I’ve run against trying to incorporate LLMs into complex and unknown (to me) projects. By the time I’ve sufficiently hunted down and provided the context, I’ve read enough of the codebase to answer most questions I was going to ask.
I have the same model, powering 3 machines with an average load of ~125w when it switches to battery power. I have a NUT host on one of the servers which will broadcast the outage for the other machines and the whole stack shuts down after 30 seconds and switches off the UPS at the very end. Gone through about 4 or 5 true power events now and double that in testing (overzealous I know) but the UPS is 2.5 years old now and is doing just fine. I have a spare battery because I heard ~3 years is normal but so far no indication it’s reaching replacement yet.
I think the important thing for these is to not run them down to 0. They’re only good for one event at a time and shouldn’t constantly be switching over without basically a full day of recharging again (more like 16h to recharge).
I can see consistent brownouts and events being a problem for these little machines. I’m planning on upgrading to a rack solution soon and relegating this one to my desktop in the other room (with a fresh battery of course).
You either want mastodon which has a higher proportion of thoughts and conversations, or a classic forum which is entirely dedicated to long form thoughts and discussions.
I get that, it’s a valid point. But in OOP, objects can be things and do things. That’s kinda the whole point. We’re approaching detailed criticism of contextless development concepts though so it kinda doesn’t matter.
Properties are great when you can cache the computation which may be updated a little slower than every time it’s accessed. Getter that checks if an update is needed and maybe even updates the cached value then returns it. Very handy for lazy loading.
Haven’t lost either pair of the gen 1 or gen 3 I own. Accidents happen, let people enjoy the things they want when it doesn’t affect you in any way.
Actually, I just checked my voice assistant, it got CZM from “see-zed-em” just fine. American English settings on my phone with a PNW grey accent. In fact, saying “see-zee-em” failed more for me, thinking I said CCM or Cesium multiple times.
Hackers
I agree. Except boosts. That should die and up/downvotes should just be the thing driving aggregation. Nobody boosts enough to make a difference anyways and some apps just tie the boost button to the upvote button so the feature actually gets used as expected (if enabled). It’s already hard enough to get regular people onboard here, with all the instance and account confusion with hit or miss syncing options and instances disappearing sometimes.
Maybe nobody keeps a complete file? That way no one machine can keep a complete copy of anything let alone access it if it was stored in a single chunk of storage cryptographically? There’s already so much risk for hosts here not sure there’s a way to be safer without invasive technologies.
This was last year during the first IFT.
The odd config files on inconsistent drive should just be symlinks (I think you want hard links?) so that your repo can contain all your actual code and file tracking. If necessary, keep a script on hand that can be run when mounted to recreate broken links.
This is a very strange setup and goes against standard practice separation of software and hardware unless this is some embedded thing in which case you wouldn’t have a repo on it at all.
Yeah! Very cool that he got there, my attention was just interrupted by not really connecting with what he was saying, but I’m glad I continued watching. I’m very much locked, relating to his discussion of no inner monologue.
Eh, at least you can still take notes very easily and reinstall DE later.