smiletolerantly

Bwahaha

Idiot.

Yes

And even if you do live there.

So what. I'm sleeping, remember?

Obviously next to House. He wants his seat neighbors to stfu and let him sleep. I want the same. It's perfect.

You mean, spend 4-6 days tearing your hair out, before landing on a solution which evaluates to literally the same output as your current version, but is 10% cleaner and more elegant?

Of course you do, after all, that satisfies that itch. Well. For a while, anyways...

Oh please. Be real. Are you sure there's nothing in your flake to refactor or modularize? :)

Sorry to bother you, hope it's alright if I ask for some clarification. English isn't my first language, so I'm a bit uncertain here: is "cad" a euphemism for "racist", "pedophile", "shitbrain", "misogynist", "felon", or some equally true and fitting term I'm not aware of?

Huh - you're right. I went back to Signal's X3DH spec because I was sure I was right, but it seems I misremembered how the "prekey bundles" work: Users publish these to the server, allowing (in my original assumption) for the server to just swap them out for a server/attacker-controlled key bundle for each Alice and Bob.

However, when Alice wants to send Bob an initial message and she gets a forged prekey bundle, Bob will simply not be able to derive the same key and communication will fail, because Bob knows what his SPK private key is, while the server only knows the public key.

A compromised server would allow the server to man-in-the-middle all new connections (as in, if Alice and Bob have never talked to each other before, the Server/Eva can MITM the x3dh key exchange and all subsequent communication). That's why verifying your contact's signatures out-of-band is so important.

(And if you did verify signatures in this case, then the issue would immediately be apparent, yes.)

Edit: I was wrong. See below.

That's why safewords should be passphrases! /s

Hold on, actually no, not /s

It's a very steep curve to start, with some additional minor steep parts along the way, but it's not a long curve. Once you got the core concepts and the basic language constructs, you've learned most of what you'll ever need.

Two nice resources: search.nixos.org is super handy, and you can search GitHub with language:nix and a search term to get tons of examples from other people.

Oh, and nix and just is actually a pretty common combo!

Yep, exactly.

To be fair, if you use Debian, Arch, Fedora,... long enough, you also know how to tweak your machine for every purpose. In Nix, it's just somewhat of a self-fulfilling prophecy, because you have to know how to tweak your system to achieve.... anything, and then it's the same tweaking mechanics for every other purpose as well.