I’m probably in a similar boat thanks to 4x NAS drives (in 2x mirror vdevs so essentially half as power efficient too). I wonder if using an SSD or two for things like caches would help with power draw since you could defer disk usage for longer by relying on a more efficient cache.

SnapRAID is also an option. One benefit is that multiple disks don’t need to be spinning at once to access data. Downside is that your parity isn’t calculated in real time so less data redundancy.

Yeah they really like to act like they’re giving away £50k on a whim and not paying someone for their labour.

It’s a pain but also it’s no surprise that DNS and ipv6 are premium when ipv4 and dynamic IP works so well for 99% of us. Even if you wanna host something publicly there are totally free services and software tools to cover most if not all caveats of not using ipv6 (for now).

I have selfhosted for years and only paid for a domain name recently.

no fucking way

metronome for the other components to practice playing songs at the right bpm

Yeah even if you’re someone who is super concerned about Jellyfin’s API safety, it’ll likely be less maintenance setting them up on tailscale than duplicating the streaming hardware. But that’s assuming OP’s family are as tech illiterate as mine

I have two 4TB in Raid 10 (ZFS Mirror) and two 8TB as the same. All in TrueNAS Scale.

TrueNAS is pretty good for a basic setup imo!

A computer. Seriously that’s it. Of course depends on your use case (media servers usually need more than a web host for example)

big up Stirling. it’s super easy to host and packed with features. one of my favourite apps

Yup. I got our QA guy to help debug it and he was like “maybe just dont upgrade the dodgy dependency and delete your cache” lmfao yup fixed it

spend a week trawling github and documentation pages only to realise you forgot to delete your cached dependencies

Rsync to a Hetzner storage box. I dont do ALL my data, just the nextcloud data. The rest is…linux ISOs… so I can redownload at my convenience.

diet pi counts right? most of the software in their managed repo is a straightforward install and largely preconfigured for daily use. It was my first server OS and im very fond of it

Oh yeah I don’t buy the backwards compat stuff because you can version an API to preserve backwards compatibility to sensible ends.

I’d be very interested to see cases of streaming or copyright lawyers essentially hacking users to litigate them. The only stuff Ive ever seen on snooping by corps on pirates it’s usually collecting PII from public sources like torrent clients without VPN coverage.

I know about adblockers but these websites are still usually ass even with them.

I don’t mind battling them for something like an F1 livestream but when you want your own collection of stuff that won’t get randomly shit on by domain seizures or ISP blocking, there’s a reason I’m self hosting my media.

They doubled the price lol. And why pay $80 for something that they have the right to gut at any time?

I use a non-rooted docker, reverse proxy, and cloudfare domain. I know Jellyfin has some API security issues but I’m still unconvinced that any of them can be used to escalate to any level that would threaten my server (or even my instance of Jellyfin).

You’re not paying for software maintenance, you’re paying a subscription service to a private company that has already decided to cut back on features that others also thought they were paying to maintain.

If you want to actually pay for software maintenance, migrate to Jellyfin and pay them instead, rather than filtering your payments through middle managers and shareholders first.

No matter how bad someone might think Jellyfin is, it is a million times better than subjecting yourself to endless ad slop on one of these ““free movies”” websites.

I have it as an unprivileged container behind a reverse proxy and HTTPS/HSTS. I know it’s not perfect but I keep backups of important shit and monitor things regularly.

I agree that Jellyfin needs to improve its API security, though. Their excuse that “it would break clients on old APIs” is moot when C# comes with API versioning features out of the box.