paperemail

joined 2 years ago
[–] paperemail@links.rocks 5 points 1 month ago* (last edited 1 month ago) (1 children)

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

[–] paperemail@links.rocks 3 points 1 month ago

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. ¯\_(ツ)_/¯

[–] paperemail@links.rocks 17 points 1 month ago (2 children)

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

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

[–] paperemail@links.rocks 5 points 2 months ago

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

[–] paperemail@links.rocks 2 points 3 months ago

That sucks, good to know.

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

[–] paperemail@links.rocks 0 points 3 months ago* (last edited 3 months ago) (7 children)

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)