Out of interest I checked again to see which app works with Atmos 7.1. Offical Jellyfin AndroidTV app and Wholpin trigger transcoding on the server. VoidTV and Moonfin play it without an issue. I know there’s an open issue on the Github somewhere, but I don’t think there was any progress there.

I’ve tried multiple Jellyfin apps for TV and all but VoidTV refuse to play Atmos with DV. 5.1 works, but 7.1 doesn’t. Including the offical Jellyfin app. It’s odd because it used to work until it didn’t.

Bread maker, if you have a bit of extra space. We got one barely used off of marketplace for €35 (~65% cheaper than new). I throw ingredients in the basket and let it do its thing for 3 hours.

I can put 15 layers on in winter and still be cold. My toes and face are the worst. If I try to protect my nose, I get snot everywhere and it’s gross. If I don’t, I feel like my face will freeze off my body. Too hot sucks as well. No winning for me except for spring maybe.

Funny you should say that.

We have a “purebred” and a rescue. The former is one of the healthiest breeds and the few genetic disorders (which can affect any breed/mix) the parents were screened for. The rescue is a mix and she already had a physical disability when we got her. For all the surgeries and care she’s needed, we could have gotten a dozen well-bred dogs. And that doesn’t account for all the stress and countless several hour trips and time spent on her recovery and treatment.

I don’t really mind, we sort of knew what we were getting ourselves into. I do wish I could find the fuckers who caused her injury and then just dumped her on the street as a wee puppy. But yeah, a rescue can cost as much or even more than a well-bred breed dog.

Internet has a hard-on for virtue-signaling and black-and-white perspective, and “adopt, don’t shop” is one of those. There is nothing wrong with ethical, responsible breeding.

There is, however, a lot wrong with unethical breeding (e.g. doll-face persians, scottish folds, pugs, frenchies, showline GSDs, etc., and backyard breeding as a whole) and official breed standards set by people who only care about the looks and not the health of the animal.

Yeah, naturally it takes getting used to. But overall I can’t imagine going back to LoL (even though I still miss Teemo and Nocturne after all this time, lol).

In reality nobody really thinks about the turn speed (unless maybe pros). The skill range is big, so the only thing that really matters is that matchmaking places you with people of similar skill.

Dota feels like LoL in the same way a wagyu steak tastes like McDonald’s burger patty. (I played LoL some 16 years ago and switched to Dota 13 years ago)

I know someone who’s 28. She doesn’t work, has a well-off partner and is behaving like a child/teenager. So uh, yeah, checks out only kids (actual or otherwise) watch him. The rest of us are grossed out by the idea and creeped out by his soulless eyes.

I think I remember this one. I was a bit apprehensive about it because it looks like it’s at least partially vibe-coded.

Not the OP, but I wanted something accessible from the browser. I found very few self-hosted solutions.

I have these two bookmarked to check out later, but haven’t tested either yet: Davis, Luna.

The bizarre thing is I already had it set up in a way it shouldn’t have hijacked it. Worked perfectly fine for a long time. Evil DNS forces at it again!

Pihole is my DNS server (Unbound + Local).

I fixed it? After the issue appeared I changed Raspi’s hostname to FQDN, i.e. pihole.my.domain. So it sort of makes sense that it bypassed Nginx. I changed it back to how it was before (just “pihole” and instead of my.domain I added “home.arpa” as local domain). And now it’s back to normal. Which makes about zero sense to me, because I basically just changed it back how it was both before and after the issue started.

Thanks for the help! It didn’t even occur to me to look if Nginx was being bypassed.

Hm, looks like you’re right. For some reason it’s completely bypassing Nginx. Traceroute to all my other proxied services points to nginx.my.domain, except pihole, which points to pihole.my.domain. There have been no changes to my configuration, this is odd.

Edit: Local DNS Record for pihole.my.domain still points to nginx.my.domain.

The FQDN resolves fine. I can still reach Pihole over https://pihole.my.domain/ and click on “Proceed to pihole.my.domain (Risky)”, but the browser fetches Pihole’s self-signed certificate instead of my.domain and throws a warning about certificate validity. Which it absolutely shouldn’t, because Nginx conf for Pihole points to port 80, not port 443.