I am sorry, but that notebook is way too modern for a proper Gentoo user. Anything above 500MHz is wasted energy with useless kernel flags

I just checked the code and unfortunately, they do not support loading the SQLite file into memory yet. Even worse, the change would be substantially. It appears they currently abuse the database connection a bit. They basically create a new connection for each operation. This does not matter if you can read/write in parallel, but that’s only the case with NVMe and certain drivers. So all SATA (SSD and HDD) suffer from the current mechanic. So just loading it into memory is not going to solve the issue. Jellyfin needs to change architecturally, so that a database connection is reused. I don’t know why or who implemented the current logic, but it is clearly done by someone not understanding how databases work.

Depending on the mood and time, I will come up with a solution that is solid. For now, you are stuck with the current logic.

Oh god. I had to save this image and now I will use the sticker version of it everywhere.

Tate molesting jailbait?

How large is the database? Because there is a way to fully load SQLite into memory, which would speed everything up drastically for a scan. At the end of the scan, you could just write back everything to the disk, then it is just one blob of sequential write, which is fast enough on spinning rust.

It is a discussion about the UNIX philosophy and architecture and it is not about functionality. That’s why it seems to be a bit short-sighted. However, I do understand both sides, but I would never go this far and create a website to promote my views and opinions. It is as if you had a discussion between team emacs and team vim.

Even though that the reliability of OpenRC is 0.00000001% higher, they keep forgetting about operational costs. And since my day only has 24h, I’d rather be able to copy&paste an installation script from the Docker website (which includes systemd commands), instead of manually writing it and losing 30min of that day.

But you know, to each their own. I love OpenRC, I love systemd.

I was genuinely looking for alternatives to systemd, just because I was curious.

I stumbled upon: https://nosystemd.org/

The anger sits deep. What a beautiful sight.

FYI: they use Claude Code.

Just in case anyone has an issue with that.

Yeees, to the arena, go fight my little Pikachu and make me proud!

Capitalistic pigs can’t be normal, because money > morals, but only until a civil war starts where people hunt those pigs down. I am eagerly waiting for this.

Just a couple of posts above was the news about the Mullvad CEO being a white suprematist. ‘Nuff lemons.

I had long discussions with some mailcow contributors and it turns out, that some default settings can lead to an open relay if you are not careful. The biggest problem is that they use postfix. Postfix is not bad itself, as it is probably the most battle tested mail server. The configuration of postfix is a different story. And even if I prefer battle tested GNU/BSD software, postfix would be one of the rare exceptions where I would be careful.

I had a postfix running for years without issues, when I self-hosted SimpleLogin, and I fully agree with you. Once it runs, you only need to make sure that the security is managed.

I used mailcow, got an open relay immediately. Stalwart seems to do things a bit better.

I host so many services and it is not that I don’t want to learn new stuff. The effort is simply too high for a single service. And since there are very good providers which fully encrypt your data, I went this route to keep my mind off this part of my system.

One wrong config entry, and you have an open relay and a domain that can never be used for SMTP again, yay.

Actually managing an email server properly is demanding, as it is one of the most attacked services. Of course, you can also take the easy route and just pray.

Jellyfin people who constantly ask “have you tried Jellyfin?” have never used Plex and don’t know what they are missing out on.

I have Emby lifetime. I have Plex lifetime. I try Jellyfin every year.

Plex wins always. Emby is second. Would not recommend Jellyfin.

I would never trust a newly written email server and there is absolutely no reason not to use an already existing as a dependency to this project.

Tell me again why a properly managed container environment (if you wanna go bonkers use Jails on FreeBSD) offers more attack surface than multiple operating systems running the exact same software.

Just randomly mentioning ISO27x tells me exactly that you have absolutely no idea how those standards work.

You should look into container technology. No reason to have this many operating systems wasting resources

Yeah, stupid me realized that too late.

laughs in unattended-updates. On Debian, not Crapuntu