Keyoxide proof: $argon2id$v=19$m=64,t=512,p=2$/Bxo7QiXHH/MThwxZ1irnA$S8IDyQY5+tRZjnqvqnYcGQ

  • 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
rss
  • Sadly with The Talos Principle 2 they moved their entire studio to the Unreal Engine 5 and retired their own engine in the process. Apparently they lost a few engineers working on the engine and also couldn’t have kept up with modern engines without some serious investment (no pun intended). On one hand it’s probably for the better as we got a really pretty game where they could focus more on the game instead of bringing the engine up to speed but it’s also sad to see the entire industry converge around engines like Unreal.





  • I guess it’s good to mention alternatives but imo Kyoo seems to be overkill for a homelab use case as its design goal appears to be to scale much better and serve a high user base and huge library. Just looking at the dependencies or compose.yml should make this apparent.
    Consequently the setup is much more complex and heavy to run compared to Jellyfin e.g.


  • I could mention that my bare metal server runs a rather unusual setup in that I use Arch Linux on ZFS headless as a kvm hypervisor and lxc containerisation host. I maybe want to migrate it to something else like NixOS at some point since I use nix on Arch on my desktop already but since I know Arch the most of any Linux distro I just went with it and it’s running rock solid for quite a few years already.








  • Basically servers and Pis.

    If you wanted to host your own site and services, a Linux vps was (and still is) the only choice. Back then it was Debian, nowadays I use Arch on everything. Same with Raspberry Pis when the first one became available in 2012. With university I started using Arch on my laptop and later when Proton and Wayland became good, I moved to it on the Desktop as well.



  • I learned that using nix on arch for the home directory in addition to pacman and the aur is quite an unbeatable combo that I prefer to having everything managed by nix. The problem with nix and nixos I see for one is that it leaves some performance on the table for reproducibility and that many packages are or cannot be packaged for nix. Additionally arch already is quite reproducible albeit not as much as nixos. Writing your own meta package with a simple pkgbuild to manage the system base seemed like a good substitute for me.