GauntletWizard

There's a huge performance advantage, if you ask SystemD - Multiple resolutions can be cached. This is incredible bullshit, of course, but that is one of many lies Pottering has gotten away with.

If SystemD had it's way, it would. The local system resolver cache is the default on most systems. DNS is well understood. Why not put it in the Kernel?

If you're doing that, though, you'd better dang well give me secure key storage in the Kernel, too, or full TLS capability. Allow my program to n load it's RSA/ECC key at startup, then drop privileges to access that file, and have a kernel module handle the cryptography.

I'm an Ex-Google SRE. Kubernetes is not Borg, will never be Borg, and Borg does not need to borrow from k8s - Most of the "New Features" in K8s were things Google had been doing internally for 5+ years before k8s launched. Many of the current new features being added to k8s are things that Google has already studied and rejected - It breaks my heart to see k8s becoming actively worse on each release.

A ton of the experience of Borg is in k8s. Most of the concepts translate directly. The specifics about how borg works have changed over the years, and will continue to change, but have never really matched K8s - Google is in the business of deploying massive fleets, and k8s has never really supported cluster sizes above a few thousand. Google's service naming and service authentication is fully custom, and k8s is... fine, but makes a lot of concessions to more general ideas. Google was doing containerization before containerization was a thing - See https://lkml.org/lkml/2006/9/14/370 ( https://lwn.net/Articles/199643/ doesn't elide the e-mail address) for the introduction of the term to the kernel.

The point of k8s was to make "The Cloud" an attractive platform to deploy to, instead of EC2. Amazon EC2 had huge mindshare, and Google wanted some of those dollars. Google Cloud sponsored K8s because it was a way to a) Apply Google learnings to the wider developer community and b) Reduce AWS lock-in, by reducing the amount of applications that relied on EC2 APIs specifically - K8s genericized the "launch me a machine" process. The whole goal was making it easier for Google to sell it's cloud services, because the difference in deployment models (Mostly around lifetimes of processes, but also around how applications were coupled to infrastructure) were a huge impedance to migrating to the "cloud". Kubernetes was an attempt to make an attractive target - That would work on AWS, but commoditized it, so that you could easily migrate to, or simply target first, GCP.

The front page of hacker news is not where I expected to see Gura fanart today.

A computer is much more likely than your body to have small, self contained parts that just function. Your body is the result of millions of years of accidental evolution - See the canonical example of the laryngeal nerve in a giraffe. Computer programs are often designed to be small and modular. They might have to worry about memory layout shifting because some other program grew - That's nothing like your spleen trying to occupy the same physical space as your stomach and causing digestion issues.

For all of medical science's experience and history with debugging the human body, there's still so much more to understand.

Yes, it's the most obnoxious behavior I could think up - Which meant I was sure it was correct, but not the kind of sure I'd want to rely on.

I also refreshed myself on snprintf, and as un-ergonomic interfaces go, they did a good job with what they had... But I will gladly take my golang multiple return values, now that I have them.

    So, only when the returned value is non-negative and less than ‘n’, the string has been completely written as expected.

Pass keys are a solution that will probably win, because it's very attractive to the device developers. They're portable, from one device to another, but only using the developer's private apis.

U2F is better cryptography - the device key never leaves, but this is precisely what makes it hard for users. Losing a U2F key is risky, yet you have to carry it around with you. You can do what I do - Have a second U2F device registered everywhere, so that if the travel one is lost,

But I just experienced the second pain- I had a phone die on me. This seriously messed up my life for a week - every provider that used phone verification or text verification was inaccessible.

As developers, I beg you not to go to exclusive Passkey support. Keep UN/PW/U2F support around, and support multiple second factors.

Really, the problem is as simple as this: there's way too many bad actors, they have knowledge of tech, and little risk.

It's not the art style, it's the poor execution of the art style, and the

The remaster re-rendered the original cutscenes pretty much intact, but at higher resolution. They look terrible. Why? Because they're higher resolution, but no higher detail. A low resolution video, your brain fills in the details. "There's cracks and crevices in that wall" you think, looking at the blurry image of a stone texture. When it's high res without any filtering or texture improvements, it looks terrible.

The character motion is limited by number of frames. In the original, the characters moved smoothly, pixel to pixel. The low detail art and the low resolution that it was presented at worked because they fit smoothly together. The remaster? High resolution low detail sprites look like they're gliding across the landscape, even though they've got more frames than before.

You're living the dream, man.

Not a chance. This level of infrastructure was set up days in advance - I would be unsurprised if they'd had a code freeze all week for this fight.

Grafana doesn't take up gigabytes unless you're doing something crazy; it's about 100mb in my small business deployments. Which still might be too much for your $6 VPS! I would still highly recommend Prometheus, as it's native dashboard has gotten a lot better with 3.0

I'm going to give it my best guess- it will copy up to n bytes, including the null byte if present in n, but not adding a null if the nth byte isn't a null, requiring you to set the last byte to 0 manually, whether that's allocating n+1 bytes or truncating the nth.

Someone else might come to your house and open your fridge and use butter with a label that says "Ingredients: Milk" and not realize you received mislabeled butter.

The logic is very easy: Certain groups objectives are not "Everyone lives well" or even "I live well", they are "I live well in comparison to those I see around me". They do not say it aloud and they are not very bright, but by their actions and what compromises they are willing and unwilling to accept you can eke out their true utility function. They thrive in chaos because they receive relative pleasure from seeing others fall, and even more from importing the miserable and keeping them miserable.

To be perfectly honest, everyone does this. Schadenfreude is an inherently human trait. The relative weight is different by person, though.

Yes, exactly that. Or anyone who hacks their Github account.

I'm not sure you can call a group most noted for its "Role in 1984 bioterror attack" a success.

From the GitHub UI, very simply. Go to a repo you administer, in the /tags page, and each tag has a ... Drop-down menu with a delete option. Then upload a new tag by that name.

Tags are not automatically updated from remotes on pull (they are automatically created locally if it's a new tag). This doesn't mean that the remote can't change what the tag points to, only that it's easy to spot.

Edit: and to be clear, for many years after release, this was the recommendation from the Visual Source Safe team (Yes, that team developed GitHub Actions) for managing your actions. Tell people to use "v1", then delete the tag update it each time.

Does it matter? In the modern sellout world, by the time something can be considered "Mainstream", it's already well on the way to abandoning the principles that made it successful in the first place and replacing them with "Cost Effective" practices and monetization, what used to be called Selling Out and is now termed "Enshitiffication".

It does not matter whether you're talking about the broadcast and cable television media (ABC, NBC, CBS, Fox), the new wave media of online-first reporting (All the properties of Conde Nast and Ziff Davis, incl. Wired, Vice, Cracked, Buzzfeed, etc.), or even the third-generation blogosphere (Substack, Medium). There's no trust because success is inversely correlated with trustworthiness.

The same as the difference between the Department of Redundancy Department and the Bureau of Standard Acronyms

http://www.alexandraerin.com/2015/05/fiction-the-redundant-m...

No, I'm not. I've got a bunch of yubikeys locked in lockboxes when they're not in use, serving as trust anchors for internal PKI, but also using certificate logging. If one is compromised, there's a short window until it's known, and access to the box has a very small group of people. My threat model does not include "Insider under the watchful eye of two other insiders"

I've got several Linux gaming machines (and a couple of business desktops I play FTL on sometimes), and it's weirdly inconsistent - the best and worst machine I have both use Intel Graphics. It almostnever shows up on the A770 - that one stays awake for weeks of daily gaming and I have no problems with it. My laptop with integrated Intel sees it all the time. My laptop with Nvidia graphics sees it often, but not nearly as often.

The one that's so annoying that I've actually developed habits around it is the tendency for the library window to freeze when it becomes unfocused - it's not all the time, but it's often enough that I now habitually close the window anytime I defocus it

I would gladly take an old stock yubikey at a discount - my threat model doesn't have a serious need for resistance to stolen keys, because at the user level they're unlikely to not notice them missing for long enough to successfully attack and then replace to a keychain.

If I could get ECC ram for my consumer hardware, I would - but I'm not paying the xeon tax to store my photos, in addition to the necessary 20% premium for the ram sticks themselves, for my personal workloads.

I'm much less worried about storage hardware failures than other parts of the process scribbling over memory that sqlite has mapped. Being able to detect incorrect software behavior, regardless of the source, is useful in its own right.

Is he, though? When was the last time you heard that sound?

All of the games on this list comprise the "Buy SEGA Mega Drive and Genesis Classics" and "Dreamcast Collection" bundles. My guess is that part of it is the emulation layer - They use a shared backend and launcher for the Genesis games. Maybe they couldn't come to a license agreement with the emulation developer?

The standouts for me are Jet Set Radio and NiGHTS into Dreams. The former is well known for it's soundtrack; Ain't nothing but a funky beat. The latter is unique and doesn't quite work, but there's something compelling anyway about the dreamlike visuals and weird floaty gameplay. Crazy Taxi is one I loved as a kid, but it's a bad port - an "Enhanced Remake" that ruined the game by leaving out it's killer soundtrack and breaking the controls.

https://store.steampowered.com/bundle/10143/SEGA_Mega_Drive_... https://store.steampowered.com/bundle/14082/Dreamcast_Collec...

I am a network engineer who understands what those acronyms mean, and what you're describing is an order of magnitude more complicated and more work for the average use case in a large corporate environment, a small business environment, or a home network environment.

This is not simply architecture astronomy, it's the equivalent of planning an expedition to a planet to plant a flag with a title granted by the "International Star Registry"

You don't choose EKS because it's easy to manage. You choose it because you intend to use the bevy of other AWS hosted services. The clusterfuck of management is directly related to that.

The alternative, which I feel is far too common (and I say this as someone who directly benefits from it): You choose AWS because it's a "Safe" choice and your incubator gets you a bunch of free credits for a year or two. You pay nothing for compute for the first year, but instead pay a devops guy a bunch to do all the setup - In the end it's about a wash because you have to pay a devops guy to handle your CI and deploy anyway, you're just paying a little more in the latter.

Hetzner: https://www.hetzner.com/dedicated-rootserver/#cores_threads_...