Text:
I consent to Plex to: (i) sell certain personal information (hashed emails, advertising identifiers) to third-parties for advertising and marketing purposes; and (ii) store and/or access certain personal information (advertising identifiers, IP address, content being watched) on my device(s) and share that information with Plex’s advertising partners. This data is used to deliver personalised ads and content, ad and content measurement, audience insights and product development. Your consent applies to all devices on which you have Plex installed. You can withdraw your consent at any time in Account Settings or using this page.
Soure: https://www.plex.tv/vendors/ (Might have to clear cache)
Can also read about the changes here: https://www.plex.tv/about/privacy-legal/
I’m a big fan of Jellyfin. I would say it is easily family approved. That is for my family in my household who is using it on our home Wi-Fi.
But I am not about to expose it publicly. I have WireGuard set up on my immediate family’s devices and that is mostly ok (until you get on a public Wi-Fi that fails because you haven’t gone through their portal and can’t because the vpn is on, or you are on an airplane’s Wi-Fi with no internet trying to watch their movies and it doesn’t work until you turn off the vpn). Explaining this to my wife has been a nonstop battle.
I’d like it open it up to my siblings families, especially because I have the ersatztv plug-in to create approved child stations, but so many smart tvs and devices don’t support a vpn. How have others handled that situation?
Wireguard doesn’t necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.
If you configured your wireguard profile to always route all traffic over the VPN then yeah, you won’t be able to access local networks. And maybe that’s what you want, in which case fine :)
But you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.
This second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else’s WiFi) and your home network.
For this reason if you want to do this it’s best to avoid on your own home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*
I reconfigured my home network to 192.168.22.* for that reason. Now I never hit conflicts and VPN can stay on all the time but only traversed when needed :)
I typically use split routing BUT also have dns set to my pihole, both so dns works for my internal services and for tracker blocking. That causes a big issue. Also I wish WireGuard would just handle failures better. Even when it can’t connect, it seems to break networking (at least on iOS)