The remote server only has the latest version of the package, and the latest version is always built against the dependencies on the remote server. So if you didn't update the database, then your pacman -S command will fail, because it can't find the package version on the remote server. So you did not install anything.
No, pacman -S package is safe. Because the package list is not updated this way, and therefore the system is not updated and nothing else is affected. New packages can be installed with this command, perfectly okay. That is in the spirit of Archlinux.
If the package is not in your cache, it needs to download it from the remote server first. The version on the remote server is built against the dependencies on the remote server. So if your local dependency is older, it will be a partial update!
But -S package is not upgrading the package. Installing with that command is supported. That is NOT a partial upgrade of the system. -Sy package is considered a partial upgrade, because that command updates the package list.
I disagree. The -S flag stands for "sync", which means sync the local version with the remote version. So if there is no local version it just installs the remote version. This is still a partial update, because any dependencies it might have, that you already have installed, might be the wrong version compared to the one the newly installed package expects.
pacman -S should be discouraged because of this. The correct one is pacman -Syu for installing new packages.
It should support NVENC according to TechPowerUp.
I have only ever used raspberry pi and intel hardware for jellyfin, so I don't know how well nvidia does when going down in specs.
Yes, but it's always the one people come back too.
They mention the other issues are either being tracked elsewhere or already solved.
At the end of the day, it's a community project, done by primarily volunteers, who is not making any money doing this. No VC funding to hire developers to take care of these issues.
From one of the Jellyfin devs in the issue you linked, posted in April this year:
Now, let's address this clearly once and for all. What is possible is unauthenticated streaming. Each item in a Jellyfin library has a UUID generated which is based on a checksum of the file path. So, theoretically, if someone knows your exact media paths, they could calculate the item IDs, and then use that ItemID to initiate an unauthenticated stream of the media. As far as we know this has never actually been seen in the wild. This does not affect anything else - all other configuration/management endpoints are behind user authentication. Is this suboptimal? Yes. Is this a massive red-flag security risk that actively exposes your data to the Internet? No.
At this point, this over-4-year-old issue has gotten posted to HackerNews more than enough times and gotten quite enough unhelpful peanut-gallery comments like those above.. We are limiting this issue to Jellyfin collaborators only at this point. Most of the big items are already tracked elsewhere (specifically, unauth playback) or have already been fixed. And many other options are now open to us in a post-10.11 landscape now that we have a proper library database ready.
The main difference between Plex and Jellyfin is the network setup. Plex takes care of that for you, while you have to set it up your self with Jellyfin.
Another difference is that Plex can combine content from multiple servers ( I think. I'm not a plex user, so I don't know for sure), while it will always be seperate servers in jellyfin.
Jellyfin will always have my heart though, because it's open source and not here to make money. Plex also have a reputation to show ads and other stuff from streaming services.
I went:
Pi 2 -> Pi 4 -> Odroid H3 -> Intel N100 box (current).
All in all from about 4W idle on the pi to about 10W idle on the N100 box. So not a big power jump all in all, but my needs did get bigger since the Pi.
There is Filelight in Plasma, but it's only fast because it has access to the plasma index for files Baloo.
I use ncdu extensively though. Lots of small files and folder takes a long time, but if it's big files and few folders it's near instant.
The remote server only has the latest version of the package, and the latest version is always built against the dependencies on the remote server. So if you didn't update the database, then your pacman -S command will fail, because it can't find the package version on the remote server. So you did not install anything.