Inspired by this post I spent a couple of hours today trying to set this up on my toy server, only to immediately run into what seems to be a bug where <video> tags loading a simple WebM video from right next to index.html broke because the media response got Anubis’s HTML bot check instead of media.
I suppose my use-case was just too complicated.
People have audited the APIs and it is a known issue that if you know the correct URL to certain resources on the server (e.g. specific files) you can fetch them without authentication. Nothing more serious than that has been found.
I would trust the FOSS software’s actually auditable security any day of the week over the sketchy proprietary solution targeting an extremely niche market.
For some reason they recommend against directly forwarding Jellyfin’s ports, but reverse proxies are fine. I expect this is because the default configuration doesn’t use SSL.
This smug mentality that security is unnecessary when exposing ports to the open internet reminds me of people who think its fine to drive drunk because “I’ve done it dozens of times before and nothing happened!” It also reminds me of the mentality of tech company VPs right before they have a massive data breach. It’s quite absurd to read.
I think you’ll find without exposing ports to the open internet we would not be having this conversation right now. Which, I suppose, wouldn’t be such a bad thing.
It does not say that in the documentation. What the documentation does have, however, are extensive instructions on how to make Jellyfin accessible on WAN: https://jellyfin.org/docs/general/post-install/networking/ https://jellyfin.org/docs/general/post-install/networking/reverse-proxy/
I’m not sure if you’re joking or not, but you can remotely stream from Jellyfin without using a VPN.
Abandoning streaming services only to become a serf of another commercial subscription service seems like such a bizarre move that I really don’t understand how Plex users even exist.
As far as I understand it, if the proposal was voted on and lost, there’d be a cooldown period for a certain time before they’re allowed to resubmit the same thing. The people pushing this are using a loophole of sorts where they retract the bill when it looks like it’s not going to pass and then resubmit it later with slight alterations. It’s an attrition tactic; they only have to win once whereas we have to repeal it every time.
If you’re waiting on Wayland to reimplement the thing that made X11 a monolithic unmaintainable mess, you’ll be stuck on your rotting platform from the 80s for a while.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Wayland supports so much more stuff than X11 does, and what does X11 have that Wayland doesn’t? X forwarding? Just use a modern remote desktop solution, all X forwarding was doing in “modern” times (read: the 21st century) was streaming pixels anyway, just less efficiently than modern remote desktop.
Mr ChatGPT didn’t even understand that the meme is agreeing with its anti-Wayland prompt lol.
Fairphone also lets you change out the battery very easily, so it’s not that big of a deal if it degrades. You might save the world 20% of a battery’s worth of e-waste by micromanaging your charging, which won’t really make a difference.
Using Plasma Wayland on Debian sounds like you’re deliberately setting yourself up for a lot of pain.
Doesn’t $0.36 times 150,000 downloads come out to 54 thousand dollars, which is a lot of money?