R (largely and by default) relies on CRAN, and they are extremely selective about what packages they accept, including testing new package versions against downstream packages before publishing an update, etc. That largely mitigates many of the concerns of some random 10 layer deep dependency getting swapped for something malicious.

It looks super creepy. Malicious compliance from the artist maybe?

Windows + major consoles, and Steam Deck verified via Proton.

Yep. My friend is an indie game developer and while his studio’s next release is “Windows only” (and consoles) they are testing to make sure it runs well on the Steam Deck via Proton / will be Verified.

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

They think you have a stolen ID and cause problems for you.