Nibodhika

I recently had a weird bug with Jellyfin, are you by chance using a domain name? Try accessing Jellyfin using direct IP, e.g. http://192.168.1.123:8096/

There are great apps that provides a way of organizing such libraries which you should do to have stuff organized regardless of problems with JF. They're called Sonarr for tv shows and Radarr for movies, they also provide other features, but their media organization is great

First past the post, the winner take all voting system seen in most countries

And by most you mean a dozen or so. Of which the big names are USA, Canada, UK and India, so essentially the UK and their colonies.

I don't hate it, I think it has its uses, just like text generation. They're great for brainstorming ideas or quick unimportant stuff like RPG campaigns, so for example an in-game fake company logo or a poem to contain hints for the players.

However trying to use it for anything serious and final is stupid and dangerous. IMO any artist that had their art used to train a model should be able to claim royalties on anything created with that model, regardless of whether they can prove their art was used for the piece. And if the data used to train the model is not made public or can't be verified, then ANY artist can. Maybe just 1% of the profits direct or indirect of that art, so for example you used AI to generate part of an invitation for a party, 100 artists could start a lawsuit and take every single cent you earned from the party. After all you indirectly hired them, it's only fair they get paid, had you hired a single artist you could negotiate the price with them.

H is for High Performance, U is for Ultra-Low power usage. So if you want something for gaming choose an H if you want to have hours of battery life choose a U. Pretty simple and easy to st a glance see if s processor is what you're looking for.

The 7 is not repeated on Ryzen 7 9700X, otherwise you wouldn't have stuff like the Ryzen 5 1600X. The first 7 (or the 5 in my other example) is the segment, i.e. towards which market it's directed, Ryzen 3 are entry levels that you should consider for your grandma, Ryzen 9 are high power CPUs. Then the first number of the 4 digits is the generation, the second one is the how it stacks up to others in it's series, the third and fourth are extra differentiation if needed, then there's some letters for feature flags. So for example your Ryzen 7 9700X is a high-end 9th generation high clock/performance CPU, just by that name alone I can guess that it outperforms a Ryzen 7 9500X and possibly matches a Ryzen 9 7700X. If you learn to read those it makes it very easy to figure out if an upgrade is worth it just by the model number.

USB naming convention is a mess, I'm not touching that.

Also not sure about the pro, none of my phone's ever were pro or even had a pro version so not sure.

Sony is a bit weird, but WH-1000XM5 is a Wireless Headband (WH) 1000X is the model M5 is the generation, so those are newer than WH-1000XM4, and the next iteration of them will be called WH-1000XM6. The N is as you guessed noise canceling, the 1000X are top of the line so they have it too, no need to advertise it. I don't know much about other products of them, but they do seem weird.

Monitor names can be very helpful, for example Dell uses [Series][Diagonal][Year][Ratio or Resolution][Features] so just by looking at a short code, for example I'm not even sure this monitor exists but a U3224QWC is an ultrawide QHD 32 inches IPS with anti-glare monitor released in 2024 with a USB-C input. That being said https://www.reddit.com/r/funny/comments/j5pezf/computer_monitors/

Ook

I mean, yes, but there are ways around it. Windows could have a public key embebed somewhere and the private counterpart gives access, the command could depend on the time it's received, so it's never the same and without the private key it's impossible to reproduce, and the Killswitch could be non-instantaneous, combine all of that and you have a Killswitch that:

• It's very hard for you to realize something happened, because by the time it happens the trigger is lost in a sea of other requests
• Even if you were to fine comb through all of that and spot it, it's encrypted
• Even if you were to resend it it would do nothing, because the time has changed
• Even if you managed to find the public key and decrypt it the actual content could be inocuos, like a random looking string
• As long as the private key is secure enough it would be impossible to crack
• Even if you somehow managed to crack it and send anything you want to the PC you don't know the protocol to generate the random strings and you only have the one example of the message (which no longer works)
• Even if several people did this the content could truly be random (in the common sense of the word, i.e. pseudo-random), since Microsoft controls the RNG on Windows they can use that to ensure that random data gets generated equally

And I'm not even a cryptographer, people who come up with new encryption protocols can surely do a lot better than my naive example above which would make it almost impossible for someone to figure out.

No need to apologize, it's a weird choice from Plex, I would have never guessed that this is how it works if I hadn't suffered outages myself, and I'm amazed that not many people call them out on this, it seems completely against what most self-hosting people are looking for, but they seem to defend Plex with teeth and nails.

First of all I agree with most of your a, b and c points, just would like to point out that while it's true that Docker containers provide an extra level of security they're not as closed down as people sometimes believe, but as a general rule I agree with everything you said.

But you're wrong about the way Plex works, this is a quote from their documentation:

So, your Plex Media Server basically “relays” the media stream through our server so that your app can access it since the app can’t connect with your server directly.

If that's not clear enough:

Your security and privacy is important to us. When you have enabled secure connections on your Plex Media Server, then your streaming will continue to be secure and encrypted even when using our Relay feature. (When using secure connections, the content is encrypted end-to-end and tunneled through our Relay. The connection is not terminated on our servers and only your Plex Media Server has the certificate.)

So it's very clear data is streaming through their relay server, which goes back to my original point of I expect that to be a paid feature, it's using bandwidth from their relay servers.

As for the security again you're wrong, authentication happens on the Plex remote server, not on your local one, which is why you can't use Plex without internet (part of my dislike for them). So you connect to Plex remote server and authenticate there, you then get a client that's talking to the remote server, even if someone was able to bypass that login they would be inside a Plex owned server, not yours, they would need to then exploit whatever API exists between your home server and that one to jump to your machine, so it's an extra jump needed, again similarly to having Authelia/Authentik in front of Jellyfin.

You are, authentication on the VPS, you're relying on Jellyfin authentication against the internet. Correct me if I'm wrong, but this is your suggested setup: [home server] Jellyfin -> [remote server] Reverse Proxy -> [remote machine] users. Let's imagine a scenario where Jellyfin has a bug that if you leave the password empty it logs you in (I know, it's an exaggeration but just for the sake of argument, an SQL injection or other similar attacks would be more plausible but I'm trying to keep things simple), on your setup now anyone can log into your Jellyfin and from there it's one jump to your home server. On Plex's solution even if Plex authentication gets compromised the attacker only got access to the remote server, and would now need to find another vulnerability to jump to your Plex at home.

Putting something like Authelia/Authentik on a VPS in front of Jellyfin is a similar approach, but the Jellyfin client can't handle third party authentication AFAIK

For remote streaming they do, here are their docs on it https://support.plex.tv/articles/216766168-accessing-a-server-through-relay/

From that documentation:

So, your Plex Media Server basically “relays” the media stream through our server so that your app can access it since the app can’t connect with your server directly.

No, the article only mentions the feature by name, the docs for the feature mentions the relay https://support.plex.tv/articles/216766168-accessing-a-server-through-relay/