That makes sense. I’ve only hosted Plex through a proxy or VPN anyway for networking and security reasons, but it’s pretty shitty to force it just out of greed.
I am also planning to move to JellyFin, but more out of open source fanaticism than financial reasons.
That isn’t how it used to work.
Why would they care what subnet the request is coming from? That’s wack.
Can you give me an example of remote direct access that would be blocked? You can use nginx to forward your public IP to your Plex and it’s fine, you can forward ports directly on your router and connect to your public IP, you can use a VPN to connect from a different network; what are they limiting? It’s the same hurdle you have to overcome with Jellyfin. Relays are convenient, but they also cost money.
You can use ZeroTier to connect from anywhere. It only makes you pay to use the plex router/relay.
If you connect with the IP address it doesn’t charge you. You can use ZeroTier to connect from anywhere.
Right, the $2 is to use the relay service, which costs Plex bandwidth. They can’t just do it free for everyone forever, bandwidth costs money.
The $2/mo is for the Plex relay service. If you access the server directly it should be free.
And if it’s SQLite (which I believe is the default) it’s really just reading and writing a file on the file system.
I have had the most issues with Nvidia gpus. Have you double checked it didn’t go back to the open source drivers after an update? Sometimes you need to download the proprietary drivers from Nvidia’s website after every kernel update.
Are you on an Nvidia gpu?
We’re just talking about the filename, the exact creation time is tracked by the OS. Plus I’d imagine most documents also have a time and date inside. The file name is mostly for sorting and human readability.
I understand you feel very strongly about four digit years, but I really don’t see any situation that I couldn’t sort out with a simple script.
Usually I don’t put dates in file names in the first place, but when I do I use the UTC timestamp; a date without a timezone is inherently fuzzy, and it’s easier to compare and differentiate numerical times.
If someone used two digit years in their naming convention I wouldn’t even blink, let alone get the woodchipper, life is too short to get angry over stuff like that.
It’s just a filename, calm down. The created by date is tracked by the file system and the repo.
The exact date of creation is usually preserved in the filesystem, we’re just talking about what to name the documents themselves. The filename should be short and to the point, it gets truncated if it’s too long, and on windows you only have 260 characters for the entire path to the file plus the name.
Here you go gramps:
(shortD) => {
return parseInt(shortD.slice(0, 2), 10) > 50 ? "19" + shortD : "20"+shortD;
}
ISO 8601 is YYYYMMDD (or YYYY-MM-DD in extended format)
Are you really going to wood chipper someone for leaving off the leading 20? I think we can safely infer the century and millennium with a high confidence, why not trade them for two extra name characters?
I always thought it was (g)o to (d)efinition.