For that reason, there should be a sysadmin in every call, who can just reboot the offenders machine

Not a reason to switch to 11 tho. 10 is still better. Linux is on the top tho ofc.

It was designed and sold for gaming. Gaming only. That’s why it’s objectively better than all recent GPUs.

Things “AI” is good for: Cheat (except much worse than doing it properly)

In my perception¹, ML differs from a brain by operating on words in form of tokens, while the human brain works by associating a concrete piece of information or thing with another, with the path in between being formed at some points, but crucially, being editable more or less easily and flexibly by retraining. And that’s the points, humans learn on a fundamental level. Dropping the prod DB means that my brain will form a hard association between the action of writing ‘drop database’ and fear, which in turn triggers deeper thoughts about wth I’m doing. LLMs see “conflict at line 1, 12”, and for some reason one possible path of tokens to generate can be a drop command. And as the underlying model data does not change, they don’t learn.

On how living being’s speech centres work, idk.

¹The perception of an acidhead. So don’t trust me.

I mean everyone looking at that equation should think that

Also, use set -euo pipefail (look at man set) in every script that’s more than four lines. It would instantly fail and exit upon finding an unbound variable.

Why can’t they just fuck?

Probably, yeah. I’d start in C and realize I do actually like C++ concepts and styles too much to continue in C.

C

Omw to switch my arch to a selfwritten init manager /s

Now I seriously hope you find out yourself.

Which means installers will now abandon their plans to ask for age at installation, and the systemd field will stay in level with other fields in terms of usefulness and usage rate. Good.

I had to enable the specific nimbus experiment for me, so it’s still in A/B-testing for normal users

And according to your /etc/passwd you are , located at , reachable under and .

I can only hope that people will someday realize that systemd did nothing more than add a userdb field, symmetric to other, similar, userdb fields, while the distro installers are the components that actually decide wherever you need to enter your data, and more importantly, if that includes an actual verification of that data.

If you want to ensure that real age verification will never be a thing, tell your distro maintainers how you feel about that, participate in relevant discussions about the installer etc. Also, support realistic pushes towards keeping it out. No, a random GitHub user won’t be able to maintain a hard Ubuntu fork without systemd. Not even for a day. However, it is possible to maintain a soft fork of the installer, minus age input, including the building infrastructure for release images.

Even if systemd would now remove the BD field, or all user info fields, distro maintainers could and would just switch to another implementation, nullifying any efforts and just worsening the situation.

I’d like a CEO paperweight. Literally just a chunk of its body as weight.

And 64 years ago, GECOS was released, with a dedicated field for a users real name, location, phone number and email. That was implemented in UNIX shortly after, as a field in /etc/passwd, which means all Linux distros and other UNIX-like OS’s like MacOS have and had fields for all of that forever. So if you don’t want the option to store personal information in your OS, use TempleOS.

Yeah, with GECOS introducing the GECOS field, they normalized name verification, phone number verification, email address verification as well as location verification. So soon we should see those becoming mandatory and controlled.

Oh wait, that was 64 years ago, so by now we should already be in literally 1984, actually?! Or is it that no one actually gives a fuck about a handful of programs trying to read user data that no one set, and if they set it, set it to a nonsencial/false value without any component verifying anything?

The problem isn’t libraries adding more optional field to their capabilites, but management systems (such as a distros installer) making them mandatory against user will. That is what users should actually object to. No installer or component I know actually sets the location field. However, some are already planing to require the birth of date field, which is the actual start to pushing any boundaries. So start protesting there.

Or, if you actually think that simple standards for how user data is stored is already malicious verification, your only option is probably, unironically, TempleOS, as even DOS stores user information, Country + TZ, available for other programs to fetch.

LUKS header disk emergency destroy button? *boop!