Nibodhika

Yup, that's exactly the problem I have, it's ridiculous that it doesn't let me stream from a local network just because it thinks that it's local network is only the docker one, it should be fairly simple for Plex to figure out it's accessible via a direct connection and it doesn't need to route through the Plex servers for this. But it won't get fixed because it pushes people to pay, hell from what people are saying here the config to fix this is paywalled so they create a problem for which they sell you the solutions.

Therefore it's literally impossible for me to watch my media locally, way to go Plex.

I don't have that configuration:

Depends on the city, here in Barcelona is very common to see Catalonia flag

Now do the same with Barcelona, just tried it and got at least one Catalonia flag, as I was sure I would since there are lots of people with flags in their balconies here. Although I don't think people are the "bad" kind of nationalist here, it's more of an independence feeling.

You don't need too much, it should be fairly straightforward, read my other reply in this thread if you want more details, but long story short it's just install docker, add your user, copy a file, edit it to suit your needs and run a command.

Docker is a virtualization platform, similar to setting out a Virtual Machine but a lot less resource intense. You need to:

• install docker on your machine
• Start/enable the service (this is usually done automatically on most user friendly distros, and if you're using one that doesn't I expect you to know how to do it)
• Add your user to the docker group

That's it, docker setup done, now you need to write a compose file, i.e. something that tells docker what do you want to run, usually you get a working example on any project website, and linuxserver.io is a great site for them too, for example for Jellyfin can be found here: https://docs.linuxserver.io/images/docker-jellyfin/

Just create a folder, create a file called compose.yaml there and put that content in it, now run docker compose up -d and congratulations you have a working Jellyfin server.

With time you'll learn what the compose file is doing, for example the ports map ports from the docker to your machine, volumes does the same, so for example the example has /path/to/jellyfin/library:/config if instead you write ./config:/config a folder called config will be created on the same folder the compose.yaml file is and inside the docker it will be mounted as /config which is where Jellyfin will look for configurations. In the same manner you can add /home/myuser/Movies:/Movies and inside docker you will be able to see the contents of /home/myuser/Movies when scanning the /Movies folder.

I can't speak for OP, but I self host lots of stuff, have literally dozens of services running, have an Ansible repo to manage it all and routi some stuff through a VPS, not to mention my day job has included managing services in one way or another for a long while. This is to say, I know what I'm doing. I couldn't setup Plex to work the way I wanted to, they expect it to run in a docker with network set to host mode, I couldn't find any way to tell Plex that my living room TV was in the same network, it just wouldn't accept any connections as local. I know I shot myself in the foot here by not letting it run with network on host mode, but I shouldn't have to, the port was exposed, I could reach it through the local network IP, but I wasn't able to stream any content locally.

I've had that happen to me with plex, it was probably 100% my fault because I specifically changed things during the setup of the docker file, but apparently Plex can't figure out that is local if it's running inside docker with non-host network, it probably only accepts local connections from the docker network, and I was never able to make it treat my actual home network as local.

Not really, if you use Kodi the information on what you have watched remains on the PC running Kodi, if you always watch from the same device that's not a big deal, but if you like to watch stuff on your smart tv, then on your PC, and downloading some to watch on your phone on the go, having the information of which episodes you've watched on the server helps keep things organized.

It's a general guideline that's accurate for average people that live average lives, but if you're too tall, too short, too muscled, have lower or higher bone density, etc it can be very inaccurate. No doctor takes any action on this alone, but it can be a guideline to ask you for blood works or other studies to ensure things are okay. There are better ways to measure body fat percentage, but that requires special instruments and also are usually dependent on where your body stores fat, so you might not have ever done them before.

The best way is asking: what's your point? Is it that transgender shouldn't be accepted or that transrace should?. And proceed from there to either defend transgenderism or criticize transracism accordingly.

First let me start by saying I strongly dislike the race therminology, but I'll use it here for consistency, although normally I would call it ethnicity.

The difference between those lies in that gender is a social construct, and race is not. Race has some biological meaning, just like sex, people can't change their sex (yet), they can't change their race (yet).

Gender is a social construct, it's things that have nothing to do with biology but that we as a society attribute in general to a specific sex. A similar concept for race would be culture, a person can be of the sex male but prefer to wear clothes usually associated with female sex, just like someone can be of the white ethnicity but prefer to hear music usually associated with black ethnicity. I wouldn't call Eminem or Michael Jackson transrace, what would that even mean?