Curious what went wrong with your Reolink run. That’s what I’ve got. Doesn’t require an app or account, and works with home assistant.

It’s not a matter of privacy vs UX. I actually think Plex has ruined their UX. But if you have friends and family, some are tech-illiterate, some have their own media servers, and you all want to share with each other quickly and easily, Plex is the only viable option. Same if it’s just you, but you travel a lot, and want to watch something from your home server without lugging around a device that has access to your VPN and a screen/hdmi-out.

Jellyfin is really only viable if it’s just you on your own network.

To add on to the top post: with Plex you only need 1 account and can exchange access to multiple servers. I can browse all the media my account has access to with ease.

Jellyfin needs an account per server. If the client multiplexed between them seamlessly, that would probably be fine enough. But it would be nice if they supported some method of federation.

And Jellyfin has a list of CVEs that they haven’t addressed in years, which makes not want to make it visible outside my network.

I want to ditch Plex, but this is the primary sticking point for me. No criticism to the Jellyfin devs btw, they’re doing the lord’s work, I have nothing but respect for them.

Another minor one is that the Plex app works with a controller on my bazzite HTPC, but the Jellyfin one was hit or miss. I could get it to work once, and then the next day the controller would do nothing and the UI would be acting weird. I will go back and try it periodically to see if it’s ready, but last time I checked it wasn’t.

As a lifetime owner, the number of features they’ve deprecated is probably the worst part.

• Photo support (luckily Immich came along)
• Tidal integration (no idea if that was Plex or Tidal’s decision)
• Plugins (god forbid anyone add the functionality they keep removing)

It’s close between that and the last app overhaul that removed a bunch of functionality.

Could you maybe elaborate on the feature parity?

1. I travel often. There are a lot of devices in hotels, bnbs, and friend’s houses that have native plex support. Not so much for jellyfin.
2. Casting to cast-compatible devices is very hit-or-miss, but mostly miss. I know the casting ecosystem is already a mess, but as far as user experience goes, Plex has spent more effort ironing it out.
3. The native Plex client works with a controller on my bazzite HTPC when launched from the steam ui, while the native jellyfin client doesn’t.

I keep trying jellyfin out every few months, but so far keep hitting enough friction that I can’t reliably make the switch.

as in separate jellyfin account per each different jellyfin server?

Yes, if me and 5 of my friends have jellyfin servers, we all need accounts on each other’s servers. I then need to juggle accounts to access their content.

Jellyswarrm is a reverse proxy plugin I could run to mask the problem for myself, but it’s not a solution for mom who may have access to my server, and one other friend’s server that I don’t know.

The correct solution is federated accounts, but the devs have already stated that they don’t want to do that.

Why would you host it openly rather than in a VPN like Tailscale or whatever wire guard is?

Then friends and family have to be on my VPN to stream anything.

To me this means they know they don’t have a viable business model. It’s possible they took on a lot of debt years ago, and now they have to enshittify to pay it back. I paid for the lifetime membership years ago, and I would say I’ve more than gotten my money’s worth and I’m mostly still happy with Plex, but I would drop them in a heartbeat if jellyfin was a viable alternative.

People don’t like to admit it, but jellyfin doesn’t have feature parity yet. I think they could solve a lot of the issues if they went the federation route, but until then, it’s just easier for my family and friends to each have 1 plex account instead of N jellyfin accounts. Not to mention the jellyfin vulnerabilities that prevent me from considering hosting it openly.

I have a TrueNas system locally with periodic cloud sync jobs to backblaze B2.

Either way, just remember to support artists when you can. Bandcamp Friday is one of the best ways I know of to fund artists in exchange for FLACs that you can legally listen to however you want to.

But I was a broke student in the heydays of torrenting, so I’m not judging using any means necessary to listen to music.

Lol I don’t know what you want man, i didn’t realize this was one of those “digging my heels in because I don’t know how to be wrong” threads. I’ll let you do your thing, peace.

Who is “we”? I’m responding to your top level comment. You just asked the creator of an exclusively client-side app whether they support encryption. Not only is it reasonable for me to assume you mean client side encryption, it’s unreasonable for you to ask for server side encryption, because there is no server. It’s a BYOBackend situation.

Now if you’re asking for client-side encryption, something like Keepass where the file itself is encrypted, you have to use some form of auth to decrypt it on use, and you can store this file using whatever backend you want, that’s perfectly reasonable. I would still consider that encrypted at rest, but at least you could maybe separate encrypted reads from writes and limit the attack surface in the event of a breach.

All phones are already disk encrypted these days. If you want disk encryption on your PC, you should enable it. Otherwise, it’s the responsibility of whatever backend you choose to handle encryption over the network.

You might be surprised how little power it’s sipping when sitting idle. Unnecessary disk accesses might be the biggest power use in those hours, but that’s more likely to cost you due to wear and tear and eventual replacement of the drive.

I recommend buying a Kill-a-watt and monitoring your power consumption on the server for a week or two. Then do some math to see how much it’s actually costing your energy bill. If it’s actually considerable, then try using tools like powertop to see if you can determine what’s generating all the activity.

Ok, I misread what you were linking to. Yeah, that’s pretty bad to allow actual streaming of content to unauthed users. I agree they should not be encouraging anyone to set this up to be publicly accessible until those are fixed. Or at least add a warning.

If I say I custom rolled my own crypto and it’s designed to be deployed to the open web, and you inspect it and don’t see anything wrong, should you do it?

Jellyfin is young and still in heavy development. As time goes on, more eyes have seen it, and it’s been battle hardened, the security naturally gets stronger and the risk lower. I don’t agree that no one should ever host a public jellyfin server for all time, but for right now, it should be clear that you’re assuming obvious risk.

Technically there’s no real problem here. Just like with any vulnerability in any service that’s exposed in some way, as long as you update right now you’re (probably) fine. I just don’t want staying on top of it to be a full time job, so I limit my attack surface by using a VPN.

If it’s just for you, then you don’t need to tackle the hardest problem of content moderation.

The second hardest problem is bandwidth. If you post something to a forum that suddenly gets a lot of traffic, without some kind of CDN intermediary, you’ll get a hug of death and/or a huge bill for all the bandwidth.

The third hardest problem is uptime. My assumption is that you want the content to remain valid forever. No one likes seeing dead links in old forum threads. So as you use it over time, anything you’ve posted over the years could get a sudden unexpected viral hug, or you have to let it die (which may not necessarily stop the hug, since everyone would still be trying to ask your server for the content).

Just making sure you appreciate how difficult solving this problem inevitably becomes. Note that discord and Lemmy Posts let you upload images, so you shouldn’t need such a service in those cases. But for random forums, it quickly becomes hard.

I was also intrigued by the introduction of the matter standard, but the reality is there are already a ton of low power, cheap ZigBee devices out there that can operate for years on a battery.

I think I’ve run into one thread/matter compatible device that I was considering, but found a HA forum thread saying their experience with that protocol+device+HA wasn’t as stable. So I didn’t do it. I’m not even sure how cheap and low power thread/matter devices can get.

It’s already solved: FOSS means I can always fork/build my own package that does what I want. That’s why I mean it’s immune.

What concerns me is the implicit association people will make between him and FOSS, and anything they believe about one will carry to the other.

I have to assume there are already people who hear “Linux” and think “ugh, I wouldn’t touch that with a 10ft pole because I don’t want anything to do with Pewdiepie”. Similarly, if he says something dumb next week, and half his audience abandons him, they’ll likely have a negative outlook on FOSS going forward.

Either way, I don’t believe FOSS’ staying power comes from meteoric rises following a fad, it comes from a natural immunity to enshittification over time. On the scale of a few of decades, FOSS seems like it’s struggling against proprietary solutions. But just like the general concept of political democracy, I think on the scale of centuries it will become the clear, time-tested, least-bad option. But I digress.

I’ve run into this issue with obsidian, but for whatever reason I haven’t had any issues with keepassdx.

When opening an existing keepass vault, on the left there’s an “Open From” pullout menu. You should be able to select your nextcloud from there. Then find your keepass file and it’ll just work.

I don’t know why, but obsidian doesn’t have the same file picker. There’s no “open from” menu. So you just have to drill into the filesystem, find the folder nextcloud is using, and choose your notes vault you’ve sync’ed in there. And for whatever reason, that seems to be the method that breaks Two-Way Sync.

I use Nextcloud + KeepassDX on android and KeepassXC on PC. Have never had an issue. Changes on desktop/phone are propagated virtually immediately across devices.