Sure, I’m not saying this never happens, but I’d argue this is the exception not the rule. Especially when it comes to DDR5 which is still quite new, so there should not be that many laptops with dead batteries with such memory around yet. It would be a different story with DDR4, not that I would suggest that they use DDR4. And the SSD form factor they used isn’t very common, so it is probably even less likely that people have such SSDs lying around. I still appreciate that they allow me to buy the machine without memory/storage.

The point of the DIY edition is that you could just reuse some old RAM or SSDs.

In theory, yes. I don’t think it is very likely that people have DDR5 SO-DIMM modules lying around, let alone 2230 SSDs. I don’t understand why they weren’t able to go for the way more common 2280 form factor for the SSD at least.

I don’t know your exact setup, but you should add the IP that Jellyfin sees when the reverse proxy makes a request. That probably comes from the IP of your Traefik docker container.

Thanks for pointing this out! I probably would have missed this, since I didn’t expect such a change for a patch release.

Their documentation mentions:

For jellyfin to know which reverse proxy is trusted, the IP, Hostname or Subnet has to be set in the Known Proxies (under Admin Dashboard -> Networking) setting.

Does this really mean, that the only way to configure this is through the web UI? This is kind of a problem when deploying it, since without the reverse proxy I can’t reach the Jellyfin server. Is there no way of doing this outside the web UI, via a config file or something?

Edit: Apparently the configuration for the proxies is stored in Jellyfin’s network.xml config file. So it should be possible to do this without manually configuring it via the web UI.

Another edit: It works. Adding <KnownProxies>[proxy ip or hostname]</KnownProxies> in place of the empty <KnownProxies/> key to that config file does the trick.

I’m not sure why you think manufactuers of SoCs (or entire phones) - which aren’t used by Google directly (as in: used by Google in their own products or sold by Google as their own product) - provide drivers to Google. They don’t, because there is no point in doing that. This is not how the Android eco-system works or the business of selling those SoCs for that matter.

SoC manufactuers sell their SoCs to companies who want to build Android phones (or they build their own like Samsung). With those SoCs they provide a BSP (board support package) that includes all the bits needed to bring up a system running on that partricular SoC. Google has pretty much nothing to do with this, except that Google recommends a certain Linux kernel version (with a bunch of Android-specific patches) for a given Android version, which SoC makers often (but not always) use as the base for their customized kernels.

It is not like Google provides the operating system including all device specific drivers to the device manufacturers. They don’t care about that at all. They provide AOSP (which is open source, so anyone can get that) as well as their proprietary stuff like Google Play etc. That’s pretty much it.

There is a lot not to like about many Android phones (or rather smartphones in general), when it comes to their openness in regards to software. And it is perfectly fine to criticize those involved, but you should direct your criticism at the correct parties. Google isn’t the bad guy in this instance.

You are talking about phones made by Google. I am talking about ALL the phones using Android and how difficult or sometimes impossible it is to use anything but Android.

That’s not what you were saying. You were explicitly talking about Google. Also, implying it is Google’s fault that other manufacturers don’t let you install other operating systems easily is pretty bizarre. If you want to complain about that, at least complain about the right companies. Those are usually the phone manufacturers and/or the SoC manufacturers. The SoC manufacturers often times are particularily problematic, since they often do not publish open source drivers at all or in a very limited fashion.

No, unlock as in: You can install whatever operating system you want. No need for “jailbreaking” on Google phones. They officially support unlocking the bootloader (and re-locking it later as well!). There are many things not to like about Google, but how they handle their phones when it comes to openness is certainly not one of them. Pretty much all other phone vendors are much worse than that (except for maybe a few small ones like Fairphone).

How about not letting Google have exclusive rights to the drivers for all the phone hardware?

What exactly do you mean by that? Google is one of the few companies that let you easily unlock their phones so you can do whatever you want with them.

It’s on April 1st, but nobody takes it seriously.

What a heap of crap.

I like Miniflux.

or a domain with a random string of characters so no one could reasonably guess it? Does it matter?

That does not work. As soon as you get SSL certificates, expect the domain name to be public knowledge, especially with Let’s Encrypt and all other certificate authorities with transparency logs. As a general rule, don’t rely on something to be hidden from others as a security measure.