You wasted a lot of words here.
You acknowledge that at the beginning of COVID, contact tracing and sterilization of contact surfaces was paramount before we knew better, going to the length of generating, or otherwise obtaining "tubs" of cleaning products for the purpose.
My entire point is that "contact tracing" is not just who you make contact with but what you make contact with. My point is not and was never that it was relevant for protection against COVID. My point was that it was a part of contact tracing. I only mention COVID at all because that is what was taught in the early days of the lockdown. A point to which you have all but plainly said, that you have also been educated on.
The miscommunication here is that you are only looking at contact tracing as person to person contact because it was relevant during the pandemic, while I'm focused on the umbrella concept of contact tracing not just for COVID specifically and that as a medical term, which it is and always has been, "contact tracing" is not just person to person contact, but also contact with surfaces. The context of the word contact, is the difference. In your view, you are seeing contact as in someone on your contact list, a person you connect with, or communicate with. In my context, contact is the act of touching or making physical contact with peoples and things, including nonphysical contact, like what happens when you share a small space with someone, you are in contact with all of the surfaces they are, inhaling the air they're exhaling.
For COVID, contact tracing and education thereof started with the full medical definition of contact tracing, including, but not limited to, physical contact to both people and objects, and sharing a space with others. Later the former part of that was dropped for COVID specifically as it was established that it did not yield any significant prevention from infection.
None of the above paragraph is in question.
My friend who sanitized their groceries on the advice of medical professionals during the early days of the pandemic did, indeed, as you say, waste cleaning products with no real gain to show for it. In their defense, at the time nobody knew that.
My point is. Contact tracing is more than who you make contact with. That was it. You're arguing something totally off topic about COVID that doesn't refute anything I'm trying to prove.
In the context of COVID, again, no it does not prevent the spread in any meaningful way, as medical science has since proven. You were, like everyone else, taught the full meaning of contact tracing during the early days of the pandemic, yet here we are. You're up on a soap box, shouting from the rooftops that it doesn't prevent the spread of COVID. A point that was never in contention. Good job. You played yourself.
I am also a Plex pass person. Multiple times over in fact. I actually have a dedicated account for my server administrator that's separate from the account I use to watch content. Both have Plex pass lifetime.
I've been familiar with this coming down the pipeline for a while and because I have Plex pass, I too, am unaffected, as are my users.
At the same time: here is a piece of software that I paid for. It's "server" software, sure, but it's just a software package. What it does isn't really relevant. The fact is that it processes data stored on my systems, processing by my systems, using my hardware, and sends that data over the Internet, using the Internet connection I pay for separately, and delivers that data directly to the people I've designated as capable of doing so.
The only part of this process that Plex, the company, has any involvement in, is limited to: issuing an SSL certificate, managing user accounts and passwords, and brokering where to find data (pointers to my systems).
You can get a free SSL certificate from let's encrypt. User accounts, authentication, authorization, and accounting (AAA), is a function of pretty much everything that you remotely connect to, whether a Windows SMB/cifs share, your email, even logging into your own local computer regardless of OS..... And honestly, brokering the connection isn't dissimilar to how torrent trackers work, DNS or a goddamned IP address punched into a browser.
They're offering shockingly little for what they're asking, and the only thing that's on the list that would be costly in the slightest is having a DNS name for the server (registration of the domain, DNS services, etc). And given the scale that they're doing these things at, the individual costs per name is literally pennies per year.
This is not a good look at all.
I have domain names coming out of my ears. I'm tempted to buy one more and just offer to anyone that wants it, to have a subdomain name under that to run their Plex alternative on, so you can get a let's encrypt SSL certificate, and stay safe on the Internet. I don't want the feds snooping into what totally legal Linux ISOs are being shared.
I just don't know how to program at all, so I have no idea how I would go about setting up a system for that. The concept would be to automate it, and have people create an account, then request a DNS name under one of my DNS domains, and have a setting if you want it to have an A record, AAAA record, or cname (if you have a ddns setup). Once the request is in, it would connect to be DNS provider and add the record for you.
The part I'd want to have as a check on the system is to make sure that you're hosting jellyfin or something from the address you submit, to prevent people from using it for unrelated purposes; but even with that.... Do I care of people do that? Probably not. I would limit how many addresses you can have per account.