lad

Yeah, I wanted to reference Dune, too, but then thought that it’s not a very rare trope. On a related note, I took a look at tvtropes and it says that in the Dune the AI didn’t wage war, it was humans that didn’t like what AI does and prohibited it. I read the books too long ago to remember if this is so ¯\_(ツ)_/¯

Yeah, but they literally used the term as used in Warhammer lore: A.I.

In Warhammer AI is forbidden on the grounds of past wars with humanity

Almost nowhere but America exists /s

Since age tends to not decrease, that may make sense: once you reach 18 you get a signed token you can use forever.

Your token might be used by someone else, though

Only last year? I thought it was the whole last decade

Or earlier, possibly

Sounds great, but as far as I know Diffie–Hellman doesn’t protect from MitM attack if there’s no trusted party to prove the integrity of keys sent. I skimmed through the description but this seems not to touch on that theme. Maybe it’s sharing public keys in person time again.

MacOS does this, but on screen recording it never shows it. Feels good to see Linux records what user actually saw

Oh, that explains it. Well, I imagine a license that also forbids people to imagine it. Fuck you and your imagination

The screenshot seems to violate the licence it contains.

I meant ‘make sense’ to mean ‘could rewrite without garbage’. Maybe I was wrong, anyway

I’m afraid, LLMs are gone a bit further from the state when such ‘poisoning’ made sense.

I’m afraid that soon this may reach a point where it will be easier for LLM to make sense of the text, than for a human, if this idea gets further development.

but what else could be representative /s

once the tool no longer works, you

… try every trick to make it look like it works, blame everyone for not using it, blame everything for not working the way it should, break some things that are made with other tools that work for a good measure (it was their fault for being too arrogant, anyway)

Reminds me of one site that said I shouldn’t use ‘git secret’ because reasons. I’ve spent quite some time to find what do they propose to use instead (that wasn’t as straightforward as in this article), turns out they provide a ‘solution’ that includes their partners’ system to manage secrets. Another bullshit, in other words

You got me, I decided to read the article later (I hope to, at least). But your summary looks about right, I don’t really expect C++ to become much safer than it is now, which is not very much. Should take a look at profiles, I love a good laugh

Edit: looked up those ``profiles’', it looks like a vague and complicated proposal that will require an unrealistic amount of undertaking. But that might be seen as being in the spirit of C++

Later: short summary of the conclusion of what the committee does (read 307 minutes)

This is almost what I need for my ancient meme folder

Now I want to start playing NMS, I’ve had it in my backlog for a while

Reasonable and viable ≠ RFC compliant

This quote summarises my views:

There is some danger that common usage and widespread sloppy coding will establish a de facto standard for e-mail addresses that is more restrictive than the recorded formal standard.