Does it actually? My VM has a lot of RAM, and Proxmox reports usage always around 90%, but that’s no matter how much RAM it ACTUALLY has, because almost all of that is cache and not strictly necessary. free -m shows Jellyfin using maybe 2 Gigs.

Domain + reverse proxy. The security issues some people here claim are significantly overblown.

1. Signal
2. XMPP
3. Matrix

In that order. I self-host both XMPP and Matrix, and I wouldn’t want to stop using matrix. Spaces, arbitrary amounts of self-chats, and so on are great. I use matrix every day.

But for chatting… It sooner or later fails you. It’s slow. Notifications break. Messages are shown as sent, but somehow do not appear in the recipient’s devices until TWO WEEKS LATER (yeah IDK, happened twice already, in different chats and directions. Best part is, I’m not even federated!). Encryption is great IF YOU KNOW SOME CRYPTOGRAPHY BASICS, and utterly confusing otherwise.

XMPP just works. Especially the calls, holy shit, I had to fight Matrix for so long to make voice and video calls work, and xmpp just… Works. Notifications are way more reliable (as in, have been absolutely perfect). I really like monocles as a chat app on Android. (The downside is: can’t decrypt old messages on new devices, and desktop clients are ugly.)

So why Signal above XMPP?

Because it’s not your fault should something ever break in a vital service. Also the encryption and privacy afforded by it a great.

I’ll second Pocket-ID.

I originally had Authentik setup. It worked well enough. However, their packaging constantly broke and no-one seemed to care.

Switched to Pocket-ID and won’t be looking back. Passkey-based OAuth was all I wanted anyways. (Also, the logins themselves are noticeably faster!)

This started off as a single file in my private nix config, to see if I could get it working at all. In that initial part, some parts were indeed LLM generated (esp. testcases based on my existing intents and failures).

When I noticed that this might actually work and be useful not just for myself though, I moved everything out manually, refactored and cleaned it up, and everything since has just been myself. I guess you’re still right though. I’ll see about adding a disclaimer to the README until I’ve gotten the chance to properly rewrite everything.

Huh, interesting. Does that work with wildcards like “put x on my shopping list”? Also, what are you using for that, if I may ask?

Sorry, I don’t quite follow 😅

What’s the problematic response?

Yay, that’s fantastic to hear!

Also, how’s your experience been with the PE? Getting a readymade device in a nice shell is appealing for sure 😅

Oh, in the demo gif, that’s via a shortcut (holding power for half a second). Sorry, can’t help with wakeword there 😅

Very cool. I’ll definitely look into that, and let you know back here :D

Glad to be of service… 😄

did you consider metaphone matching?

I did not even know about this. Sounds super interesting. Though it seems to be very language specific?

My original intent was to not rely on language specifics. But maybe we could just define additional steps in the pipeline for specific languages. Hm. I’ll have to think about this some more, but it might definitely be a great idea for a future version, so thanks for telling me about it!!

Have fun, hope this works out for you! FYI: you can also use an LLM as an additional fallback (first closest-intent, then on failure, LLM). README mentions it further down on Github.

I don’t really know, sorry :(

If you want to migrate, is going conduit - conduwuit - continuwuity (first version) - continuwuity (current version) maybe an option?

I went with continuwuity and am happy with it. Development happens at a steady pace, with sane priorities. The server is stable and I haven’t had any issues to speak of, despite one minor bug that got resolved very quickly after creating an issue.

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.

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.

My Steam Deck also runs NixOS.

Because this way I can much more comfortably configure it, plus everything game related I automated through nix for my Desktop (e.g. mod installs, reShade config,…) immediately and without any extra steps also applies to the Steam Deck.

https://github.com/Jovian-Experiments/Jovian-NixOS

Yes. Everything is NixOS. Because it’s perfect for everything.