@Mountaineer
@aussie.zoneTOTP is a defined standard, specifically RFC 6238.
But I still have 3 different apps on my phone so that I can get on to various customer VPNS. 🤷♂️
Can't tell if you're joking, but a Request For Comments is effectively a proposal for how a process should be performed.
Some of them are eventually ratified as internet standards by the IETF.
Plenty of them remain useful as defacto standards even without formal acknowledgement.
Short answer no.
Plex works by having a centralised server run by Plex themselves, that facilitates your client connecting to your server.
The external facing part of Jellyfin server is basically a web server, and it's a bad idea to expose that to the internet without putting a reverse proxy in front of it (hence the mention of NGINX above).
Another option is to have a VPN connection to where you are running Jellyfin and then only access Jellyfin pseudo locally (so potential security problems aren't a big concern). This introduces other complications if you want to access it remotely via things like Roku or Chromecast, especially if you have multiple external (and probably not tech savvy) users.
I want to stress that none of this is prohibitively expensive or hard, but doing it involves learning and effort.
All the information and programs you need are available online for free.
If you only wanted to use Jellyfin at home (server in the cupboard, client on the tv), none of this other stuff matters. If you want to access Jellyfin remotely, and the idea of running a reverse proxy or a vpn server with the corresponding exposed ports and domain configuration sounds scary, Jellyfin is probably not for you.
You can interoperate with googles RCS.
If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).
Google are determined to not make it easy, and I agree with you, it appears to be yet another messaging land grab.
Trying to put myself in their headspace for a moment, one justification for making it hard is to stop thousands of apps coming out declaring "full RCS support!" through the APIs, then screwing the pooch (through poor security or deliberate back doors or or or).
Right now Google are desperately attempting to make RCS happen, after almost a decade of trying and failing to make various carriers play ball.
They do not want any bad press about how feature poor/insecure/slow/buggy it is right now.
Only Google can make an RCS app
Yes and no.
You don't need to make your own OS, but you do need to implement support for the RCS protocol within your app, rather than piggyback on Googles APIs.
I don't like it, but there's no legal requirement for google to provide those APIs, like they did with SMS etc.
pihole blocks ads by refusing to return dns results of known ad hosting URLs.
Chromecast ignores your DHCP supplied dns UNLESS 8.8.8.8 and 8.8.4.4 are inaccesible.
People who's bothered to do this have added static routes to make all requests on port 53 go to the pihole.
https://www.reddit.com/r/pihole/comments/uaov2a/how_can_i_override_chromecasts_hardcoded_google/
I'd guess the fine line is "Valve intend to earn money from something official in the future"
Windows XP is basically firmware at this point, and has been for over a decade.
Lots of proprietary hardware that works perfectly, will not work on newer versions of Windows due to lack of drivers.
I see it constantly in factory situations with scales, scanners and robot controllers, it would only be worse for million dollar x-ray machines.