Jellyfin can’t go closed source as it’s a fork of Emby from before it was closed source, licensed under the GPL. They don’t own that code so they can’t change that license, thus the whole project is GPL. In addition, Jellyfin isn’t being developed by just one company (it’s all volunteers), so every new contribution is also GPL licensed, owned by each contributor. The only way Jellyfin could go closed source would be to cut out the Emby backend and for every single contributor ever to agree to change the license, or have their code cut out. In short it’s not happening, and if somehow it did the project would just get forked regardless for everyone to switch to (the community did it once already!).

For me it’s the 3 actions per turn. So much nicer to still have a turn even after I rolled an attack and missed.

Your approach won’t work if you’re behind carrier grade NAT or you can’t open ports. My landlord provides my internet so I use tailscale (with headscale on my long distance vps) to connect everything and it works great. It uses LAN when I’m home, and NAT punches when I’m elsewhere.

Entirely depends on who’s publishing the image. Many projects publish their own images, in which case you’re running their code regardless.

Yes but there are ways to protect against that. For instance you can configure Tailscale clients to only trust nodes that have been signed by trusted nodes, or something like that.

This is why in my game the first order of business each session is scheduling the next session.