kuberoot

Oh I would hope not, it's good practice to not let the person writing the code merge it in, to get a fresh pair of eyes on the code before it goes in.

Though in a way you could say he "fixed a bug" by merging a bugfix written by somebody else, but that feels like a failure of attribution.

If I understand correctly, it's a different kind of "immutable", since distros like Bazzite provide premade immutable images you use and anything else you need you install using alternative means, whereas NixOS is an immutable image generator that requires you to set up your own definitions for the image, but also lets you install software by adding it to that image.

The game, including worldgen, will still bug out at longer distances - the issues were reduced and a world limit was added to prevent you going too far, and IIRC past a certain point the world turns into non-stop ocean, but I'm pretty sure if you bypass those limits you'll encounter chunks that outright fail to generate.

I believe they've made the point that it's not chrome's fault, but the site's/user's - images displayed on websites should be webp to benefit from optimizations for displaying images, but download links should be a different format. The error would be either the user downloading the images from the display instead of the download (including from sites that do not offer images for downloading purposes?), or the website not including separate versions for download where relevant.

I'm not necessarily sure if that's a good take, but that's my interpretation of what's being said.

In-memory kernel patching is complicated, AFAIK only select distributions support it, right? If kernel hotswap is successfully implemented this way, it should allow switching between arbitrary kernels at runtime without extra work or setup.

Of course, that's a pretty big "if", but a simple unified system sounds like a great thing. And of course there's more to this than swapping kernels.

I, for one, value even this mundane history of low importance, and appreciate knowyourmeme for documenting the origin, development and variations of memes.

It's a shame peoples' creations and ideas are stolen with no credit under the excuse of memes just being like that, but that's not a fight I could win, so trying to document that information seems like the best we can do.

The issue with Lua's and/or in this context is that they don't work if false or nil are valid values. In a and b or c, if b = false, the result is always c.

I also love null-related operators like ?? and ?. for this, since they explicitly check for null, letting you handle any non-null values for optional/default values. The syntax can get a bit cursed, like maybeNull?.maybeMethod?.(args) in JS, but I still prefer that to writing out multiple field accesses in an if condition... And arguably the code is only less readable if you aren't acclimated to it.

All that said I do really appreciate Lua's simplicity, as a language that provides tooling to create the features you want instead of building them into the language, though I wish it had some conventional regex instead of its own patterns.

What the fuck did I just witness? No, really, can somebody explain?

That actually sounds like a fun SCP - a word that doesn't seem to contain a letter, but when testing for the presence of that letter using an algorithm that exclusively checks for that presence, it reports the letter is indeed present. Any attempt to check where in the word the letter is, or to get a list of all letters in that word, spuriously fail. Containment could be fun, probably involving amnestics and widespread societal influence, I also wonder if they could create an algorithm for checking letter presence that can be performed by hand without leaking any other information to the person performing it, reproducing the anomaly without computers.

I disagree, runbacks are as much difficulty as having to recover your currency after death, or even having to recover your items after dying in Minecraft. It's a punishment for dying, and a way to make you treat it seriously.

It can incentivise the wrong things, punish experimentation and make players stick with what they know, even if better options exist. You're free to dislike it, and it has downsides, but dismissing it as "not difficulty" is just dishonest.

I'm not a security expert, but to my knowledge that's the point - even a unique salt global to your site/service can help. Worth mentioning are rainbow tables, which are databases of hashes for known strings, so you can take a hash and look up the string, and very easily defeated by salts.

If the password is securely hashed, and the attack only includes data exfiltration, then there's theoretically no risk of breaking into users' accounts anyways. However, the issue is that if somebody can log into your Plex account, that means they got your password somehow - and if they did get that password, they can use it elsewhere. So if there's any reason to change your password on Plex, then there's just as much reason to change that same password elsewhere.