If you’re like me, you’ll eventually find it in a place that makes no sense whatsoever.
Like with a travel toothbrush, or in a utensil drawer, or with your last phone’s USB cable, idk.
Bonus point if you buy a replacement and find the old one’s hiding place when putting the new one in that “place you’ll never forget for sure, but totally just did”.

“I can punch you in the face so you need the stitches” would be my answer.
Although odds are I’d only come up with it a few days later in the shower.

It’s to highlight something fucked up that’s sometimes done on women after giving birth.

Quoting another comment in the thread:

the Husband Stitch is a real thing that used to be pretty commonly done regardless of what the woman wanted and often without her foreknowledge or consent. It’s an extra stitch or two placed when sewing a woman back up after a vaginal tear or episiotomy during labor. The purpose is to make the woman “tighter” so her husband can still enjoy having sex with her even though she’s given birth, which is staggeringly misogynistic and cruel. And it usually results in really painful sex for the woman because her vaginal opening is artificially small plus now it has inflexible scar tissue.

Not too long ago, this was also “offered” in the case of my sister.
The extra yucky part is it was offered to her husband without even her knowledge or consent.

Nice.
If you’re gonna respool it, try not to put too many knots in there and maybe wipe it clean with IPA and a microfiber or something.

Stored in vacuum bags with dessicant?
Or stored on a shelf in the open?

Either I’d buy one known good roll to calibrate your printer, then take it from there with he old stuff, see how good/bad it is.

A filament dryer might something to look into.
There’s also a case to be made of not buying more filament than you can use to avoid these situations where you’re stuck with old sketchy stuff.

Still better than photobucket’s broken link placeholder.

I was gonna check my Steam library for the numbers, but the real answer probably is Shattered Pixel Dungeon on my phone.

The theory was FIFA wanted some batshit amount of money for the franchise which EA decided not to cough up.
This hasn’t been confirmed as far as I know, but either way it’s greedcorp vs greedcorp.

It’s not even an acronym, it’s a sportsball game by EA.

Some subjects you might wanna look into.

1. NAT hairpin, also called NAT loopback If you’re sending packets to your ISP’s public IP from inside your LAN and it fails, your ISP modem (or whichever device does the NAT, probably doesn’t support NAT hairpin.

2. Split-horizon DNS That’s when you configure your own DNS for your hosted services, but with a different config on your LAN (which would point towards your services LAN IP) and another config with your public DNS provider (which would point to your public IP)

3. Carrier NAT This could break your chances of having a reachable service as they likely won’t make a port forwarding rule for you in their stuff.

4. IPv6 address types Link-local addresses are within fe80::/10 (kinda similar to how 169.254.0.0/24 is used in ipv4). This IP wouldn’t be reachable from the outside.
   Global unicast addresses are all in 2000::/3, this would be reachable from the outside.

5.IPv6 DNS Make sure to configure both A (ipv4) and AAAA (ipv6) records with the right info. Although if your LAN devices only have ipv4 addresses and you’re doing Split-horizon, you could theoretically omit the AAAA on your LAN

6. Phone DNS shenanigans.
   Some recent phones ignore the DNS they receive through DHCP and instead use something like Google’s which breaks split-horizon and can confuse troubleshooting. This wasn’t in the SSID settings, but in a global “private DNS” setting.

As for your problems, it depends.
There might be a way to make this work without the VPS, but I don’t have all the info.
That said, a VPS or something like a cloudflare tunnel could come in handy. I usually prefer to host directly but still, that’s an option if port forwarding doesn’t work with your ISP.
You’d configure the DNS for your services to the VPS IP and configure the VPS to reach your stuff.
Using the VPS kinda also gets rid of NAT hairpin problems although it is inefficient to go through the VPS from the LAN with the downside of not working when your Internet is down.
You can still use the VPS and Split-horizon DNS if you wanna have local availability from your LAN when your Internet is down.

Good luck

Aeropress and PopOs

Updated my journal.

No

If OP somehow needs to translate between beignes and brightness_pct.
Probably something like this:

brightness: "{{state_attr('light.kitchen_sink_ceiling', 'brightness') | float(0) /255*100}}"

I think OP might just have needed the quotes around the template brackets in the yaml.

mTLS is great and it’s a shame Firefox mobile still doesn’t support it.

Oh… I think you also need double quotes around template brackets when used as the value in a service call…? Which conflicts with the quotes around the entity and attribute so just use single quotes there.

brightness_pct: "{{state_attr('light.kitchen_sink_ceiling', 'brightness')}}"

Just whipped up a partial example with my living room lights. It is missing a trigger and an else butI focused on theactionyou had trouble with.
Using brightness instead of brightness_pct seemed simpler. (Or at least if both can usethe same attribute…)

alias: Example
description: ""
trigger: []
condition:
  - condition: state
    entity_id: light.living_room_floor_lamp_1
    state: "on"
action:
  - action: light.turn_on
    metadata: {}
    data_template:
      brightness: "{{state_attr('light.living_room_floor_lamp_1', 'brightness')}}"
    target:
      entity_id: light.living_room_floor_lamp_2
mode: single

Hmmm if it’s just complaining about expecting a float, you could maybe get away with simply multiplying by 1.0

{{state_attr("light.kitchen_sink_ceiling", "brightness") * 1.0}}

I think… {{state_attr("light.kitchen_sink_ceiling", "brightness") | float}} also works these days.

My lights return brightness=None when they’re off… and None * 1.0 probably breaks something, so this might be more consistent: {{(state_attr("light.kitchen_sink_ceiling", "brightness") or 0) | float}}

PS: I can’t say much about brightness_pct, I normally use brightness instead (0-255).

Until it is done