The company owns legal liability for anything you do on their hardware.

The end.

This is what I was trying to find for op. Well done!

To a USB adapter? How in the world did that ever happen?

There’s a project on github just for this, I forget what it’s called.

Basically they’ve developed a mechanism for providing instructions and access to security (usernames, passwords, etc).

I’ll see of I can find it

Right?

I think the last TV I bought was 5 years ago, a 65", 4k, for about $650.

And I didn’t shop, I was tired and sick, just needed a replacement and didn’t care.

You’re the exception among Apple users.

I say this with nearly 4 decades in IT. Most Apple users are even more clueless than a typical Windows users, which is saying something.

I hear BitTorrent with that name

All Season tires rarely do well in snow at all.

Combine that with the torque of an electric and it’s no fun in the snow

Nokian Haakapaliita tires.

Nothing like them in the snow, and especially ice.

I’ve tried every three out there, nothing compares.

As I’ve said elsewhere, they make even overpowered FWD cars with an open diff go, turn, and stop even in icy conditions.

Very carefully.

I suggest a fully-enclosed space with near-normal earth pressures and air mix. Makes for faster adjustment and less likely to get winded.

I’d have multiple spaces connected to a central space, all with plenty of views to the outside (with appropriate solar blocking in the “glass”).

In the main area I’d have a well stocked bar, with moon/solar system themed drinks. Make it an open bar, anyone who can afford to get there has already paid.

Basically, not much different than hosting on earth, just needs to have a softer floor and walls as people experiment with reduced gravity.

What’s an “advertisement” on the internet look like?

Imagine the shit storm had a man said something similar.

Sad for both of them.

Let’s clarify some things:

When you say “server running and connected to my TV”, do you mean the computer running jellyfin is physically connected to the TV by a video cable (HDMI, DIsplay Port, etc) or your server can see the TV on the network?

And I can’t make heads or tails of this:

The TV and the server recognize the file, but the library file is empty.

To clarify, Jellyfin is a media streaming server, which Jellyfin clients can connect to and stream from, over the network.

If you want an app on a computer to play media direct to a TV via a display cable, I’d use something like Kodi, which is designed for that use-case.

“Smart” tv’s are notoriously bad at being supported by things like Jellyfin clients - it’s not the devs fault, but because the TVs are so inconsistent with what works.

So if you’re trying to stream video from your Jellyfin server on your TV, you’ll need the appropriate Jellyfin client app on your TV. If your TV has an app store, look there first. If you’re on a Samsung there’s a version you can install manually to Tizen-based tv’s.

https://forum.jellyfin.org/t-jellyfin-on-samsung-tv-tizen

My experience with Ubuntu is it’s a serious performance dog, at least as bad as Windows, and the devs intentionally left out some components because their paradigm is… unique (eg left out all the remote access infrastructure because although it’s intended for mass deployment, no one will ever need remote access to support those systems).

After 3 months of fighting their bass-ackward thinking, I dumped it for all the far more sensible distributions.

Also, Jellyfin runs fine on Windows, though since it’s a server Linux is a better choice, especially virtualized or containerized.

Yep.

I run Tailscale on every device that can run it, and have a TS router in one device at home for devices that can’t run it.

Its my fallback if Syncthing ever has a Discovery server failure.

It’s a fantastic app, but doesn’t do sync like SyncThing or Resilio Sync.

It can do things similarly if you work at configuring it, but it can never monitor a remote and sync based on file changes there. That’s not a criticism, it’s a function of the file system approach it takes - it can sync with many different file systems, but it doesn’t have a client at the other end - it simply interfaces with that file system. Fantastic actually.

I’ve used it since about 2010, it was my solution for moving files back and forth for a long time. I still use it for specific things, but I’ve put more effort into ST and Resilio Sync config and management because they’re full-on sync suites.

Instant sync only works for local folders it can monitor. Since it doesnt have a client on the other end, there’s no way to make this happen (it would have to monitor the destination).

This would require keeping a connection open between devices, which is a high cost from a network (and especially battery) perspective.

Its a great app, I’ve used it for 10+ years, paid for it 2 or 3 times because it’s worth it.

I’ve been using Fork for years. Möbius on iOS has financial support from a 3rd party that uses Syncthing in their own processes, so I suspect it will stay around.

That said, Resilio Sync is the other most-viable option I know (and use).

It’s a little less kind to battery with larger folder pairs, and uses more memory since it stores the index in RAM. But it’s robust.

Doesn’t exist, sorry.

Has to do with how RCS works. It’s a crappy “protocol” that’s bound to hardware and software like Google Messages.

Best to move on from it - it’s was born dead on the vine.

🖕

Nothng official, sorry, wish I did!

Mostly personal experience. But that experience is also shared among a group of peers and friends in the SMB space where their clients think they can keep stuff on externals in an office safe only to find they’ve gone tits up nearly every time they pull them out a couple years later. And not the enclosures, the drives themselves - they all have external drive readers for just these kinds of circumstances.

In the enterprise you’d get laughed out of a datacenter for even suggesting cold drives for anything. Of course that’s based around simple bit rot concerns, and why file systems like ZFS use a methodology to test/verify bits on a regular basis.

If nothing else, that bit rot should be enough of a reason to not store data on cold drives. It’s not what drives were designed (or tested) to do.

Edit: Everything I’ve read over the years suggests failures happen as much from things like lubricants hardening from sitting as from bit rot. I’ve experienced both. I’ve seen drives that spin up after ten years but have numerous data errors, and drives that just won’t spin up, while their counterparts that have run nearly continuously are fine (well, their bit-rot was caught by the OS and mitigated). With a running drive you have monitoring, so you know the state.