Gaming is fine, I haven’t noticed any issues but I have to admit that I’m a casual gamer at most. The monitor supports FreeSync and refresh rates up to 165Hz.

I haven’t compared VA to OLED yet, but the latter costs at least twice as much where I live. For me personally, I don’t think that’s worth it. My previous monitor was a Samsung CF791 with Quantum-Dot but honestly I find the iiyama to have nicer colors. That’s highly subjective of course and the CF791 was released roughly 10 years ago, so take this with a grain of salt.

I’ve been using VA Panels for a long time because of that IPS glow. My current main monitor is a iiyama GCB3480WQSU-B1 and I’m pretty happy with it.

I have an offsite NAS where I run the Restic REST server as a docker container. I connect to it over Nebula but you could also use a traditional VPN, Tailscale, Headscale, Pangolin or whatever.

Works like a charm.

Interesting, I didn’t know that. Thanks!

Uhhh, I have always used Docker for Home Assistant with no issues? That being said, I’m no HA power user at all - so maybe you could elaborate about the limits you’ve encountered?

I was recently reading a lot about these because I wanted to use three Lenovo M920x for my homelab as virtualization hosts with Proxmox.

The really cool thing about them is their low power usage, that you can easily buy them used/refurbished and that you can fit a small PCIe expansion card into them.

I didn’t use them in the end because sadly 22110 M.2 SSDs don’t fit and I wanted to use enterprise SSDs for Ceph.

However, your use case seems simpler, so I’d think a M720q or maybe even M710q (without PCIe slot) would do, for less money than the M9xx series (which support vPro).

There’s a really nice forum thread on ServeTheHome with loads of information about these units.

Uhh, interesting! Thanks for sharing.

No, it isn’t.

EDIT: I quickly want to add that Jellyfin is still great software. Just please don’t expose it to the public web, use a VPN (Wireguard, Tailscale, Nebula, …) instead.

I don’t know anything about Android AOSP, so I found this clarification important:

This does not mean that Google is making Android a closed-source platform, but rather that the open-source aspect will only be released when a new branch is released to AOSP with those changes, including when new full versions or maintenance releases are finished.

Electron. Many apps nowadays are just headless browsers and browsers are huge and complex. It’s nice from a development perspective, because you can (re)use web tools for desktop apps but it’s very resource hungry.

It’s been a while since that I set this up, so take this with a grain of salt. I have these two plugins installed:

• Chapter Segments Provider
• The older Intro Skipper

I’m honestly not sure if I even need both - maybe the Chapter Segments Provider is unnecessary, even though it’s official and newer. I don’t understand exactly how it works from the docs.

However, Intro Skipper gives you a new scheduled task named “Detect and Analyze Media Segments”. Use this to extract metadata about media segments from your library.

Now that the server knows about some media segments you need a client that can handle them. I’ve had success with the Android TV App (check the settings) and the Web interface should support them too.

I didn’t need to configure anything aside from that, as far as I can remember.

The media segments feature has been released as of 10.10.0 and it still needs a plugin. Still feels a bit clunky but works already on my Android TV box. I guess there will be more polish in future versions, now that the groundwork is done.

… Nebula…

HTTP 418

You need more Excalidraw in your life.

We will have more salespeople next year because we really need to explain to people exactly the value that we can achieve with AI. So, we will probably add another 1,000 to 2,000 salespeople in the short term.

Well, good luck!

I can’t wait for the AI bubble to burst. It’s going to be hilarious to see these kinds of CEOs falling flat on their faces. Unfortunately, it will not be the CEOs who will suffer the most from the consequences.

I can recommend Restic with Wasabi S3 as cloud storage backend.

I’d say ask the original developer directly. Getting your changes merged upstream should be the preferred option for you, the original dev and the users. If everything goes right, you both could figure out a way to do this, maybe by re-introducing your refactorings and fixes one by one in smaller pull requests. Maybe you could become a maintainer in the process and support the original dev long term so everybody wins.

If the original developer doesn’t respond or declines you could think about bringing your own fork forward. Think about the consequences though, the original dev might get frustrated by a competing fork and abandon the project completely. The users on the other hand might be confused or insecure about which version to choose. Your fork must offer a lot for them to jump ship and switch.

Generally I’d say open source is about working together, not against one another, so just shoot them a message and see where it goes.

Kill it before it lays eggs!

Having a solution that works for you is never a bad thing.

Now it comes down to what you want to archive: Do you want something that just works? Great, you’re done - now go on and do some other things that you like, that’s perfectly fine. Or do you want to learn more about servers, virtualization, linux, networking and selfhosting in general? Then there are a million ways to get started.

I’d suggest to setup a little lab, if you haven’t already. Install Proxmox on your server and run CasaOS inside a virtual machine. Now you’ve learned about hypervisors and virtual machines. Afterwards you could create a second virtual machine to play around - maybe install debian and get used to the linux cli. Install docker manually, run some apps using docker-compose. Now you’re already doing some stuff that CasaOS does under the hood.

The possibilities are endless, the rabbit hole is deep. It can be a lot of fun, but don’t force youself to go down there if you don’t want to.