It really doesn’t do much and the cost is barely pennies per user when you operate at scale. The largest costs will be for the DNS resolver service and the domain registration, both of which you are already required to have, in order to have a functioning presence on the Internet. The cost of the issuing intermediate certificate is probably the largest single cost of the whole operation.

To be fair to Plex, they run some intermediary (caching) metadata servers to offload the demand their users put on services like the tvdb and IMDb. Honestly, is probably not required… But they do it. (I’ve seen their caching system fail more often than either site, so, it’s not all good), but even with that, you can put most of that load into your existing webhost, and it’s unlikely to make an impact on performance.

When you do this stuff at scale, the costs of simply having it set up, usually cover the costs of using it for thousands, if not tens of thousands of users.

I have two pieces of paper from my time in post-secondary education. One says information technology, the other says business. I’ve worked in an IT field for well over 10 years in a B2B capacity. I’ve had to handle cost/benefit and ROI arguments with customers, and justify having them spend incredible amounts for their own good.

Are we done dick measuring about what we think we know?

Listen, we’re not going to agree on this. I couldn’t give any fewer shits if you do or not. Bluntly, I’m unbothered.

Good day to you sir.

I have a very good knowledge of business operations.

They already offered Plex pass to earn their income. Plex is an extremely price elastic product, given that alternatives like jellyfin exist. They are taking features away, and charging people if they don’t want to lose those features. That’s a really good way to piss off your existing userbase (or customer base). Better would be to offer something new, and charge for that. Keep existing products at the same cost, but have “better” products at a premium. You won’t get a huge number of people buying the extended product, but it will likely be more new paying users than how many you would get with the crap they’re doing now, and they wouldn’t lose any customers in the process.

When you understand the social and economic factors here, this is a super idiotic move. When you’re only looking at how many dollars you can extract from the customer base, this is a golden idea… I mean, it will fail, but it looks golden if you’re only looking at the money numbers.

I would question whether you know how a business works (or whether Plex does, for that matter).

As far as I’m concerned, Plex failed to read the room. They were already walking a fine line with the people in a legal grey area, which comprised a good amount of their customer base (those that are sharing media at least). There’s a nontrivial number of people who share media that are rather paranoid with reason. Nobody wants the RIAA/MPAA to have any reason to investigate what you are doing on the Internet. We all know how well that goes from the whole Napster thing. So now than a few are almost tinfoil hat level of paranoid. Many have already jumped ship to jellyfin or something similar. The rest are either unconcerned, not paying attention, or simply don’t care. I would argue that the numbers of people who run servers currently that host content using Plex, that are not looking at alternatives because of this, is pretty damned low.

Plex alienated the group that brought everyone into their umbrella. When the people who host media entirely abandon their product because of this shit, their client base vaporizes.

Can’t have a product or company with no clients. At least, not for long.

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.

I just upgraded to a Xeon E5 v4 processor.

I think the max RAM on it is about 1.5 TiB per processor or something.

It’s not new, but it’s not that old either. Still cost me a pretty penny.

I think I’ve already watched this. Interesting stuff.

Pretty much everything gets it wrong in stone capacity. Some get very close, but fall short of representing radio in reality.

Just don’t.

As a qualified amateur operator, I’ll just say: that problem isn’t exclusive to die hard movies, nor die hard 1.

I had to stop playing when I saw the review for AC 3 (I think) from Zero punctuation.

He pointed out that the quests were almost entirely “gofer” quests… You know, you go over there and get that, then go fer that other thing and go…

I started the game not long after and I have to say, he was right. And every time I was given a quest to go somewhere only to talk to someone with little to no reason for doing so other than, I have nothing better to do in the game… When that happened, I heard his voice in my head talking about how annoying gofer quests were.

It annoyed me, and I stopped playing as a result. Never got past the first chapter.

One thing that was recommended to me by someone a while ago, is that, unless you need it for something specific, mount your media in Plex as read only.

Plex has functions where you can delete content from the library from their UI. If you need that for some reason, obviously don’t make it read only. If you’re hoarding the data, and therefore never delete it, or use an external system for deleting files, then RO all the way.

The only caveat to this is if you’re using a local disk on the Plex system, which then shares out the drive/folder for adding new content, in which case, you’re screwed. It has to be rw so the OS can add/remove data.

In my case, as I think may be common (or at least, not rare), my back end data for Plex Media is on a NAS, so it’s easy to simply have the system running Plex, mount that network share as RO, and you’re done. The data on the NAS can be accessed and managed by other systems RW, direct to the NAS.

Since Plex is exposed to the internet, if anyone with sufficient rights is compromised, in theory, an attacker could delete the entire contents of your media folder with it. If you limit RW access to internal systems only, then that risk can be effectively mitigated.

Depends on the UPS. Many cheap offline UPS units don’t. Anything line interactive or online will.

APC makes low end offline UPS units, which are cheap garbage.

They also make line interactive and online ups units, which are decidedly not completely garbage.

I pick up line interactive APC units from used locations like eBay, and go buy off label replacement batteries. Haven’t had any problems with them so far.

To date, over the last ~10 years of running a homelab, I have used mainly SMT 1500 units, one was a rack mount. I’ve recently upgraded to an SMX2000. I’ve replaced batteries, but never a UPS, and never any server components due to power issues. I’ve run servers ranging from a Dell PE 2950, to a full c6100 chassis, plus several networking devices, including firewalls, routers and PoE switches. Not a single power related issue with any of them.

I moved my DNS to a pair of raspberry Pi 3’s running bind, with a DNS stub zone for my homelab domain that points to my homelab DNS servers.

That way the internet keeps working whether my homelab works or not. Keeps the wife aggro down.

You can do whatever you want. Don’t let anyone tell you it’s “wrong”. A big part of homelabbing is to try stuff. If it doesn’t work, that’s fine, you learned something, and that was the point.

For me, I don’t see a UPS as essential. It’s generally a good idea, but not strictly essential. My servers are on 24/7, because I have services that do things overnight for me. I also know that some people access my lab when I’m not awake, so I just leave it on so it can be ready for anything at any time. It poses some unique challenges sometimes when running stuff that’s basically 24/7/365.

Be safe, have fun, learn stuff.

I’m generally more of a Debian user, when I use Linux at least, so anything red hat based doesn’t even occur to me to recommend. I generally don’t get involved in distro discussions though.

My main interaction with Linux is Ubuntu server, and that’s where my knowledge generally is. I can’t really fix issues in redhat, so if someone is using it, I’m mostly lost on how to fix it.

There’s enough difference in how redhat works compared to Debian distributions that I would need to do a lot of work to understand what’s happening and fix any problems.

I dunno if I’d say any distro of Linux is really beginner friendly.

It takes quite a bit of learning the ins and outs of operating systems before Linux makes sense in any capacity.

If you’re just looking to run a few basic apps like discord/slack/teams/zoom, and run a browser, then sure, just about every distro can do that without trouble, and can be configured to be as “friendly” as Windows, with a few exceptions.

But anybody who wants to do intermediate/advanced stuff with little to no prior Linux knowledge? I’m not sure any distro is much easier than others. Again, with a few exceptions.

The exceptions are distros that are almost intentionally difficult to use, or that require a high level of competency with Linux before you can attempt to use it.

There’s always a learning curve, that learning curve is pretty much always pretty steep.

I’ve been using Linux for dedicated servers for a while and I don’t use Linux as a desktop environment, in no small part because despite having a fairly high level of competency with Linux, I don’t feel like I know enough to make Linux work for me instead of the other way around.

Yep, I’m sure they do.

Realistically, does any average consumer know what’s on which circuit?

Spanning the split phase will screw you up, across breakers won’t be fun but shouldn’t pose any serious problems, as long as it’s not in different sides of the split phase.

I’m pretty sure they say this because actually explaining what will work and what won’t either requires significant prior knowledge of power systems, or a couple of paragraphs of explainers before you can get a rough picture of what the hell they’re driving at.

Everyone I know who has used powerline, just plug it in and see if it works. Those who were lucky, say it’s great and works without issue, etc. Those who were not lucky say the opposite.

I’m just over here watching the fireworks, eating popcorn.

I’ve been doing IT work for more than a decade, I was a nerd/“computer guy” well before that. I’ve had a focus on networking in the past 15-20 years. You learn a few things.

I try to be humble and learn what I can where I can, I know that I definitely do not know everything about it, and at the same time I try to be generous and share what I’ve learned when I can.

So if you have questions, just ask. I either already know, or I can at least point you in the right direction.

It definitely sounds like you have some challenges ahead. I personally prefer MoCA over wireless, simply because you can control what devices are able to be a part of the network, and reduce the overall interference from external sources and connections.

With WiFi, being half duplex, only one station can transmit at a time (with come caveats). Whether that station is a part of your network, or it is simply operating on the same frequency/channel, doesn’t matter. So in high density environments, you can kind of get screwed by neighbors.

MoCA is also half duplex (at least it was the last time I checked) so having a 2.5G MoCA link, to a 1GbE connection (on the ethernet side) should provide similar, or the same experience as pure ethernet (1G full duplex)… The “extra” bandwidth on the MoCA will allow for each station to send and receive at approximately 1Gbps without stepping on eachother so much that you have degraded performance.

However, it really depends on your situation to say what should or shouldn’t be setup. I don’t know your bandwidth requirements, so I can’t really say. The nice thing about ethernet is that it on switched networks (which is what you’ll be using for gigabit), the. Ethernet kind of naturally defaults to the shortest path, unless you’re doing something foolish with it (like intentionally messing with STP to push traffic in a particular direction). The issue with that is that ethernet doesn’t really scale beyond a few thousand nodes. Not an issue for even a fairly large LAN, but that’s the reason we don’t use it for internet (wan side) traffic routing. But now I’m off topic.

Given the naturally shortest-path behavior of ethernet, of you have a switch in your office and you only really use your NAS from your office PC, you’ll have a full speed experience. If nothing else needs high-speed access to the NAS, you’ll be fine.

Apart from the NAS or any other LAN resources, the network should be sufficient to fully saturate your internet connection. So the average WiFi speeds should be targeted towards something faster than your internet link (again, half duplex factors in here). I don’t know your internet speed so I’m not going to even guess what the numbers should be, but I personally aim for double my internet speed for maximum throughput on my WiFi as much as I can. The closer you can get to doubling your internet speed here, the better. Anything more than that will likely be wasted.

There’s a ton to say about WiFi and performance optimization, but I’ll leave it alone unless you ask about it further.

Good luck.