paperemail

Luckily there’s a support group for all the Ay-Ay-Rons and Dee-Nices out there

I can also recommend an excellent blog of the same namesake: https://theluddite.org/ Some I like:

• Need, Want, and Agency: Mapping the Digital User Experience
• Dave and the Spectacle of Computation

This is how I fucking find out???? 😭😭

I prefer the Crime of the Century. That piano riff…

I don’t think it is cropped? There doesn’t seem to be a signature or watermark or whatever on the original either.

So I guess you did your best on this one. ¯\_(ツ)_/¯

Hey OP, please credit the creator if you can next time!

https://www.smbc-comics.com/comic/muffins

Thank you both for the recommend, they sound very interesting.

That sucks, good to know.

Looks like creating a VPN is the only option for securing jellyfin.

Not unless the reverse proxy adds some layer of authentication as well. Something like HTTP basic auth, or mTLS (AKA 2-way TLS AKA client certificates)

For nginx: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/

so if I add a user ”john” with password “mypassword” to video.example.com, you can try adding the login as: “https://john:mypassword@video.example.xn--com-9o0a/

Most HTTP clients (e.g. browsers) support adding login like that. I don’t know what other jellyfin clients do that.

The other option is to set up a VPN (I recommend wireguard)