Fleet Commander 🚀

• Fleet: 6–10 devices · 11–20 TB
• Motivation: Privacy & data ownership, Independence from Big Tech & subscriptions, Learning & experimenting
• My MVPs: Jellyfin, Home Assistant, Immich, Proxmox VE, nixos-mailserver

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.

Haha. Might have slightly exaggerated. But only slightly.

The Proxmox host in question has a 1Gbit connection to the NAS. (Unfortunately. The other hosts don’t have a GPU, but SPF+… Oh well, can’t have everything.)

At some point in the last couple of months, it must have been damaged, and negotiated down to only 100Mbit. This must roughly have coincided with the Jellyfin 10.11 update, since I remember thinking that it must be the cause, due to close proximity of update and first issues.

Anyways. For basically everything in my library, 100Mbit is fine. Streaming an episode NAS->Jellyfin and Jellyfin->TV at the same time basically never saturates the link.

BUT, from what I’ve gathered by digging through Jellyfin issues and PRs, there’s a separate issue where Jellyfin will pull the episode, and if you need subtitles extracted from the episode file server-side (to transcode them in, if the clients can’t play them), it will at the same time pull the episode AGAIN, and together with the Jellyfin->TV direction, that’s frequently enough that it saturates the link.

Symptoms is (was) either a 20-30s wait before the episode would start playing, or complete freeze.

However, I believe this particular issues has been solved for a while. I’m not sure, because I instead opted for the Subtitles Extractor Plugin, which runs nightly and pre-fetches all the subtitles and stores them on the Jellyfin VM itself.

Where it was still noticeable though was if one of [Library Scan/Trick-play Extraction/Subtitle Extraction/Media Segment Scan] ran while playing an episode, the server would completely lock up.

Long story short: cable swapped, 1Gbit, all issues gone.

Sorry, but why not just fetch a single media file with multiple languages?

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

Can’t speak to that, I’m not involved. All I know is that,

• Jellyfin server gets significant upgrades in subtitle capabilities and performance,
• Jellyfin AdroidTV just released an RC that finally includes direct play for ASS/SSA subtitles,
• and on Monday, I FINALLY resolved a hardware issue (faulty cable) that made my Jellyfin almost unusable whenever ASS/SSA needed to be played (and only in that situation. Fun!)

So yeah, I don’t know or really care about leadership change, I just know it’s gonna run like a rocket now 😄

Now THAT is a changelog.

Really excited about the query performance improvements, and the improvements to subtitle handling.

I kinda wish we could federate jellyfin instances. Just manually, with friends I trust. Would instantly expand everyone’s catalogue.

No, absolutely with you on this! I didn’t mean that I don’t understand because you can simply change the string (because agreed, most people don’t know and can’t be expected to know about this).

What I meant is: in 20 years of FF usage, I have come across ~5-10 broken sites (legitimate or UA, doesn’t matter).

So I can’t understand when people say they can’t use FF because it breaks so many sites.

So I have little understanding when people say they can’t use Firefox because pages break.

goes to prove the depths of the lack of technical illiteracy that the western world has been shepherded into.

Just to be clear: I don’t mean that I expect most people to know about user agent strings. I just cannot confirm the “so many sites don’t work!” complaints, flat out

Same here. I also can count on one hand the occasions where a site was broken in FF but worked in Chromium. And for a majority of those, that was intentional (aka no actual issue, switchtig the user-agent “fixed” the site). So I have little understanding when people say they can’t use Firefox because pages break.

Not really… At least not generally. The privacy increase from switching from Android to proper Linux is, to me at least, more important than loosing a locked bootloader.

That’s just my threat model. I know that Google & Co are extracting as much info about me as humanly possible, and I have no reason to believe that I am being targeted by someone with the capability to exploit the unlocked bootloader.

Same for my PC btw - secure boot is disabled because it’s not worth the hassle. Again. In my threat model.

(But I would wager that this goes for a lot of users.)

Quick! Get this person a series A, B and C funding!

Pretty sure the Bootloader in unlockable (at least they were in the past?) and support(ed) mainline Linux kernel for an actual Linux mobile OS.

Idk, to me that sounds way better than staying on a google device.

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!)

It’s just a helper. It’s a way for your calendar to ask “uhhh… Should I already know of any calendars…?” and the service going “oh actually yeah, the user configured their email account, hold on, here’s the corresponding calendar”.

That’s just basic functionality. Maybe what’s tripping you up is that it’s a separate service? Because I assume you have nothing against inputting your email into a mail client and a calendar separately.

If so, then for one, it’s not really a difference if the mail app stores this into or the service does; and second, it’s a good thing to have this standardized into a single purpose built service, rather than having each app reimplement this stuff.

CPU and RAM usage is so negligible it’s laughable.

IDK.

It seems like you read something about personal data in the service description and just jumped to the conclusion that this is something nefarious.

How exactly is it bloatware though? Not a KDE user myself, just had a look at the wiki. Seems it’s just a convenience utility to allow you to not have to enter the same things into multiple applications?

This is VERY different from pre-installed apps in your start menu that collect and sell info about you…

Yeah, thinking more about it, I don’t think the term “bloatware” (as it is commonly used) applies here at all.

How do I completely disable it forever?

To answer your question: sudo systemctl mask <servicename>.service

The much more common disable just disables autostart; masking will point the service file at /dev/null, which makes it impossible to load or start the service, even when other services or apps (like the clock widget someone mentioned in the comments) request it.

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.