Fixed by enabling accessibility. Thanks anyway!

Think i have. Will double check

Edit: double checked. Didn’t have. Works now. Thanks :D

I’ll keep this in my head as plan B, thanks for the suggestion.

yes. I run Projectivity on my other TV and it works like a charm!

sadly out of warranty :-(

I run ytdl-sub in my jellyfin. Totally does not fit your bill, but its awesome if you just want to follow a few channels :)

By your definition not even twitter or Facebook is a walled garden.

Your definition sucks

I’ll admit that weird and unexplained data is a hint to something going wrong. Shame on steam.

How would that clearly be an outlier? Hindsight is 20/20, right?

The selfhosted guys are correct with that. Of course its not a magic pill, but it can help to minimize the attack surface immensely with little effort.

Edit: while open ports can easily be enumerated, a reverse proxy often requires knowledge of the right server name. In tls1.3 those are not transferred in clear. Depending on your threat scenario you might want to consider doh/dot etc.

Reverse proxies can require client certs, which lift the security benefit to something like a vpn. Even basic auth adds a high threshold to attackers and is simple even for random users to work with. All this is functionality many services don’t offer natively - as they assume a reverse proxy anyway I guess.

It was maybe 2003, and my Windows (XP I guess) was not working properly for like the third time this year, requiring a re-installation. I rad a home linux server (IP masquerading) at that time, and this has gotten me a student job administrating a web and a mail server, so I felt confident enough. This was when I first installed linux on my main machine. But I was dual boot or dual machine until end of 2025, when I finally got rid of my old gaming box and put CachyOS on my new rig.

Okay, a few years earlier a friend gifted me some slackware 1.0 CD, that partitioned my 800MB hdd into a 300 and a 800MB parition. The joy about the extra 300MB linux gifted me did not last too long when everything corrupted, and I went back to windows.

Using windows, which I have to do some times at work, feels so painful now.

Certainly not

no screensharing seems to work, at least none of those i tested, not even jitsi meet. i get the point of “being maintained”. but but what does it actually do better?

Idle windows is so damn heavy on io :(

Didnt find any /s there. That’s one of the reasons why I dislike docker, it supports not understanding stuff. But then that’s just me, who wants to understand stuff. Enabling less tech savvy ppl is also great I guess.

I kind of lost interest when they found out that in a distributed system you can’t delete things

Just stumbled upon this: https://jellyfin.org/docs/general/post-install/networking/

Base URL

Running Jellyfin with a path (e.g. https://example.com/jellyfin) is supported.

caution Base URL is known to break HDHomeRun, the DLNA plugin, Sonarr, Radarr, and MrMC.

so: yes, it works. but most likely: no you don’t want this.

Clearly a problem on the VM. Run

dhclient -v ens18; for i in $(seq 60); do ip a s dev ens18; sleep 1; done

Just to see if its broken immediately or if another process probably fks it up later

Use dhclient -v to See the client side, check logs in the DHCP Server. Sniff maybe.

usually port knocking opens the relevant port to the client IP that is knocking. So it makes a lot of sense to have the knocking done by the requesting client. In many situations knocking from your mobile while behind the same NAT as your jellyfin client will do the trick, but if you have different IPv6 on those devices etc, it won’t.

Also: if you assume your DNS lookups are sniffed - so are your port knocks. If you don’t, spare the extra work. But then, if you like port knocking - keep knocking, nothing wrong about it :D