Libera has cloaks by default now, as for nickserv lagging, use sasl, the tool built for this that explicitly completed before your connection to the server is finalized.
This could be interesting. Unfortunately it'd be a performance hog to do. Some kinds of things do work with this (see performance guided optimisation in compilers)
Same exists with laws. And in most languages if I want to avoid the type system and hand you a goldfish instead of an int, I can. It just may take more effort. Other language will blow up too if you hand them strange things. Just like python those languages have ways to verify you're not passing goldfish, You just may need more or less effort to use them
The point would be that if anything, storage and hardware costs have come down for large users like Google. So these cost increases are purely profit motivated, rather than due to the cost to company increasing.
The one I've used (ecoflow) has a passthrough and auto transfer option. 15ms which isn't great but I've tied it up to a small online ups and had no issues. The online ups eats the transfer time and otherwise keeps the power smooth
The funny thing here is that the "power station" market has this quite solved. Comes with an app minimum usually, which at least is a start for reverse engineering. If you're lucky you might even get a local diag socket. Unfortunately this comes with the usual IoT issues, but at least you can watch things. With better transfer hardware youd have a much better user experience for upses. I wonder why no one has done this yet.
Quite handy for doing the annoying bits of this yourself. I don't really like the private key being just available but I also don't have a solution for generating this that doesn't include private keys but is also generally useful.
I've been using radicale as my dav server for a year or two now. Coupled with davx5 it works really well on andoird and syncs well. Throw in a little wireguard and you have a nice and completely secure (for private use anyway, locking it away would make shared calendars mildly annoying)
Absolutely, just the results of the factory are not physical. You can apply this analogy quite far inside software development, engineers are factories producing data for a compute factory to further process etc. Also I'll echo warnings about factorio, you will lose days. But so very worth it.
I have a similar memory, there's something entrancing about watching a computer do a computationally (in space or time) difficult task with a visualisation about what exactly is actually happening. For defrag it was mostly a progress bar, but still it was fascinating to young me
Very cool. This kind of data visualisation can really help understand some of the intricacies of how the disk format actually puts things on disk. e.g. the metadata carefully prealloced for at least some usage. I was interested to see what would happen when it ran out of space but unfortunately the animation stopped before that time was reached
This kind of thing falls under spam. IRC networks are not your infrastructure to use for any project.
At the very least, I can tell you that Libera would define this as abuse and actively remove it. Our servers are for users to chat, not for software to communicate.
And to clarify on spam, this takes resources from the target of a given network. If that networks target is to be a platform for software communication, sure. But in general, IRC networks are there to relay chat, hence the Internet Relay Chat name. This kind of thing takes processing power away from users, and increases memory load on the server. Not to mention bloating it's services database.
I think you may have convinced me to learn more awk with this. I'd have constructed something horrible with sed or so to do this. And this is just much cleaner
This is one of those funny things. Debuggers are amazingly useful as a print statement machine. You get prints for every line. You can stop and think as the program executes. But at the same time, most bugs can be found with, as said, prints and thought.
I generally reach for a debugger when code is complex enough that I don't know where to begin putting my prints. But often end up reducing to prints and other output when I get close to the issue.
That said. For buggy code, where the bug appears seldomly, conditional breakpoints are a lifesaver.
I tend to dislike this method as it's unclear what or returns unless you already know that or behaves this way. x if x is not None else default is cleaner in my opinion