You should see the Tizen version…

Though neither are made by the Jellyfin team and they’re both dealing with the constraints of the underlying dogshit hardware/software

I have a lot of stuff self-hosted.

Just no outside access. Well, that’s not quite true, I do have a Tailscale VPN for remote management, but only certain machines are allowed to join, joins require my authorization, and access to the account is via two-factor.

The big thing with external access is to never permit it directly through your local connection. Do it though a Virtual Private Server (VPS) - let it get hit with access attempts. And then only allow specific traffic from the VPS to a specific service in your network using a VPN of some sort.

Two approaches:

Network isolation/DNS blocking - put the TV on a VLAN and only permit specific ports through to a media server (whatever the TV will support). If you lack VLAN capability, run PiHole as your DNS server (it works best as DNS and DHCP, but that’s just my opinion for things I like, such as proper name resolution for all devices).

Second option: (your idea with a Pi) disconnect TV from network entirely, then run something like Kodi (or whatever media center you prefer) on an old laptop, mini-PC, whatever, and have that device connect via HDMI. HDMI can passthrough the navigation controls from the TV remote (not guaranteed, but it’s part of the standard). I looked into this a long time ago but the performance wasn’t there yet. Today I’d probably try any distro and run Kodi on it.

Even my POS Samsung passes through enough of the controls to navigate Kodi on a 2017 laptop, while retaining power, volume, settings, etc for the TV itself.

My current setup is a Jellyfin server and Jellyfin client on the TV. I run PiHole with a blocklist for all the Samsung BS which has had the side effect of making the TV menus faster as it doesn’t retrieve any “what’s new” info from Samsung. Its actually kind of fun to monitor the FNS log and see the domains the TV hits, click Deny and see what breaks in the TV. On average about 30% of all DNS requests on my network get denied, and nothing of value has been lost. That’s how much crap is being sent all the time.

Hope that gives you some ideas.

Ah, you luddites amuse me.

The horses left the building a long time ago, and here you just now noticed and decide to play Don Quixote.

I mean it’s a commercial product - if stability issues were a common thing, that would be well known and published.

It’s a mesh VPN so it generally has the same stability challenges as any other: Hamachi, Nord, Meshnet, Wireguard (which is the underlying protocol that Tailscale uses).

If the Tailscale client is running on the NAS itself, I’d consider that the first thing to troubleshoot.

NAS’s generally don’t have much extra processing power, and in my experience apps designed to run on them aren’t the most robust. In this case, the VM/dock client has to consume all TS traffic, perform the encrypt/decrypt, put it back on the net (even if it’s only with the virtual net) over to Borg, which then has to write to the NAS. The NAS hardware has to do all this, with whatever little bit of ram it came with, also while writing all these changes, managing stripes, etc.

While they advertise these things can run stuff like this, it just seems like an opportunity for performance issues when the processing power design was for a NAS/RAID.

I have an ancient NAS on my network that could probably run the TS client, I just don’t bother. TS runs on all desktops and servers (for general access), but connectivity to non-TS devices goes through the server running as a TS router. That can be run on any device running TS - it’s just a feature to enable and configure.

I can’t imagine not using a proper internal DNS with split anymore.

I’m a big fan of Pihole (currently running it on a DietPi VM).

Being able to manage DHCP and DNS in a single place makes for much better control than the crappy DHCP from consumer routers. And almost any real DNS/DHCP server combo is better than those things.

Just rebuilt my PiHole over the last couple days, and it’s currently blocking 45% of DNS requests with no ill effects on any system - it’s a lot of Android app nonsense and a smart TV.

I’ve lost the Samsung TV service on the TV, but I never used it anyway, and the TV is so much more responsive now.

Yea, smart TV… Bad news. It’s next on the list to get a Kodi box on it.

I’m not - that’s a used price.

I don’t have a problem with used - all my drives are used, and they typically last 5-10 years. I have some drives from 2010 that are still running.

New drives fail too, so relying on drives being new to prevent failures is foolish. The only defense against failures is duplication (which 3-2-1 backup falls under).

Whats just as important is to use a file system that can detect and repair data errors (such as ZFS).

LTO tapes are 18TB today, raw - 48TB compressed.

How much data you got?

At that size I can probably build 2 Proxmox boxes with drives and compete very well on the costs.

A single 14TB disk is about $270 today - that’s in the same realm as a tape.

But tape also requires a drive, and that gets pricey fast.

This is the answer.

I haven’t done the math, but even SMB’s don’t use tape today.

They may do a local replica and then some kind of local-hardware-based cloud backup solution, because cost and capability.

Yea, getng people to do something is a challenge, let alone connecting a calendar to your server.

That’s where we should be today, but people really don’t understand how this stuff works, and won’t even try to learn even if you explain it in simple terms.

I’m upvoting for your openness and directness about your approach, what you will and won’t do.

You built this for you and are sharing, for us to do with it as we will.

It’s an interesting idea for basic printing.

Someone else mentioned just using a calendar client that can connect to different calendars.

I use Fossify to connect to calendars through Davx, which includes my Google calendar (configured it through DavX).

This way all entries remain independent. And I can filter my calendar view based on source calendar, and all entries are color coded (automatically) by which calendar they’re on.

I know it’s not exactly what you were asking for, buy it’s one way to approach it.

Or, just completely bypass any config by simply not using IP6 for an environment where it offers no advantage

But you don’t know if it’ll even power up, or if the data is valid.

Printing should be relatively easy nowadays

Hahahahahahahahahaha

I mean if you’re making a statement that after decades of maturation this should be true, I wholeheartedly agree.

If the statement is of an observation of conditions today, oh, my sweet summer child.

Even commercial, enterprise-targeted stuff is junk today (looking at you Sharp, with your supposed LDAP-capable crap that just decides to lose it’s fucking mind for no reason).

Neat idea you’ve put together though!

No.

Cold storage is really “no storage”. A cold drive can’t tell you when an area of disk fails, or when the controller itself fails.

May as well just throw away the data, because you have no idea how much will be there when you try to power it on.

I have 8TB of data, and I get bit flips - if the drive were cold, I’d never know.

And cold drives fail just as often as hot drives.

There’s no ‘wearing it down’ - age is age.

If anything, unpowered drives die faster because lubricants slowly harden over time. Ah least a running drive is unlikely to suffer that fate.

Also, any drive can lose magnetic cohesion on areas of the platter - with a running drive that’s maintained by a system like ZFS, these areas of magnetic loss can be automatically discovered and corrected.

Everything I’ve read (and from my own anecdotal experience) drives on a shelf die every bit as frequently as running drives, if not more often.

But in the end, don’t go doing anything just because you feel like “you have to”. I have a dozen smaller drives (500GB to 1 TB) that are just waiting for a purpose. I have a plan for them, but it’s not urgent. Eventually they’ll go in a Proxmox/TrueNAS/UnRAID box, when I can find a motherboard for the right price with low power draw (the drives will be the worst power consumer anyway).

Are you me?

This is the exact argument I make about updating.

Without knowing, you’re just trading known risks for unknown risks.

Known risks can be managed.

My opinion of the constant update cycle today: it rationalizes management’s liability offloading while also justifying staffing requirements and therefore budget.

Liability and risk are related, but very different things.

True.

It really depends on a lot of “what ifs”.

I’ve been through the cabling thing in multiple places since 1996…

Today I run cable as-needed. If wi-fi gets it done, I’m not putting in the effort for cable.

If wifi isn’t getting it done, I’ll run a single cable for the location with issues, and drop in a gigabit switch (if needed).

The days of running cable “just in case” are in the past, for me.

I have 53 nearby wireless networks. Lots of interference.

Channel scan charts just look like a bunch of color mixed together.

I used to modify my access points to use non-standard channels to help.

Still, other than copying media files, it’s fine.