Danke!! Endlich sagt wer was!
Are you having this argument on the principle of defending the undergrounded-ness of bands, or do you actually believe LLMs always get the facts straight?
smiletolerantly
joined 1 year ago
Imagine reading this headline and instantly jumping to this in your head.
Eh. There's memories I cherish a thousand times more because I made them with my partner.
But there's also memories I cherish because they're mine alone.
For traveling specifically, just having someone with you also isn't enough; you need to want to do the same things, in roughly the same way.
OK, add step above: use wildcard certificate for your domain.
Terminating the TLS connection at your perimeter firewall is standard practice, there's no reason your jellyfin host needs to obtain the certificate.
Actual answer for 3:
- put jellyfin behind a proper reverse proxy. Ideally on a separate host / hardware firewall, but nginx on the same host works fine as well.
- create subdomain, let's say sub.yourdomain.com
- forward traffic, for that subdomain ONLY, to jellyfin in your reverse proxy config
- tell your relatives to put sub.yourdomain.com into their jellyfin app
All the fear-mongering about exposing jellyfin to the internet I have seen on here boils down to either
- "port forwarding is a bad idea!!", which yes, don't do that. The above is not that. Or
- "people / bots who know your IP can get jellyfin to work as a 1-bit oracle, telling you if a specific media file exists on your disk" which is a) not an indication for something illegal, and b) prevented by the described reverse proxy setup insofar as the bot needs to know the exact subdomain (and any worthwhile domain-provider will not let bots walk your DNS zone).
(Not saying YOU say that; just preempting the usual folklore typically commented whenever someone suggests hosting jellyfin publicly accessible)
Holy fucking shit I am not alone. Oh god. It's real. I'm not alone.
How good is it with background activities?
About the only thing holding me back is that my phone runs a continuous glucose monitor, constantly connecting with a small sensor in my arm. That all quietly dying in the background would just... not be an option.
Not my style
Not comfortable
Too cold
Neovim, because I wanted something that would not just disappear.
I never really got along with VSCode, opting for Atom instead. Microsoft bought GitHub, which owned Atom, and promptly discontinued it.
Nvim has such an active community (and no "owner") that I'm certain that this won't happen again. At the same time, the plugin system is so flexible that I'm also certain that I will never miss out on any shiny new features.
Over the years, my config has matured, and is mine. The thought of going back to an editor, any editor, less flexible in its configuration than nvim is just... an absolute "no".
It's a steep learning curve, but well worth it.
Yyyyyyupp
"Oh no, this device is rooted! :(" Yes because I know what I am doing, now show me my account balance you stupid piece of ahit banking app.
view more: next ›
Ugh yeah, it feels like the show is making fun of Preservation, which kinda undermines the show. Contrary to what others seem to think here, in my opinion the added goofiness really detracts a lot from the show.