manwichmakesameal @ manwichmakesameal @lemmy.world

Posts

1

Comments

33

Joined

2 yr. ago

Goddamnit, I didn't even think about this when I saw they were doing the mass delete. Here's to hoping that they'll at least keep the videos up. Waaaay too much stuff on YT to lose it all. Anyone know if archive.org is backing them up?

That looks pretty cool. It’s got giant mechs so I’m in.

Different use cases.

This looks like it’s just sponsor blocking in the videos. Does this block pre/post ads?

As a Volvo fan, that was my first thought too.

US or Japan 7/11? I'm pretty sure they're different grades of coffee.

"They're not here for me"

My setup is similar. My main “desktop” is a Slackware VM through VNC/guacamole.

Why are you running full VMs for something that can be put in a container? Sounds to me (without having any evidence or proof) that you’re running out of memory and you’re swapping and it’s taking forever. That’s what causes the VMs to slow/stop.

Why not just run your own WireGuard instance? I have a pivpn vm for it and it works great. You could also just put jellyfin behind a TLS terminating reverse proxy.

I'd suggest Alpine too. Works great for me so far.

Man oh man...... Let the Right One In..... I see this thing being suggested all over the place and it just didn't do it for me. Been a while since I watched it but I didn't think it was even that good let alone good enough to suggest to anyone. Different strokes and all that I guess.

Correct. SearxNG is very much still active. Check the GitHub page or matrix/IRC.

Fuck that and fuck him. He deserves no sympathy.

Cloudflare zero trust tunnel might be up your alley. Look into that. It’s free but has privacy concerns so do your homework.

It was me. Guess what I'll be doing today.

This is the way.

Forgive my stupidity, but couldn't you just use split-horizon DNS and have your internal DNS resolve to your homelab instead of the VPS? Personally, that's what I've done. So external lookups for sub.domain.tld go one way and internal lookups go to 10.10.10.x.

So, docker networking uses it's own internal DNS. Keep that in mind. You can create (and should) docker networks for your containers. My personal design is to have only nginx exposing port 443 and have it proxy for all the other containers inside those docker networks. I don't have to expose anything. I also find nginx proper to be much easier to deal with than using NPM or traefik or caddy.

Why did you register two separate domains instead of using a wildcard cert from LE and just using subdomains?