InEnduringGrowStrong

git reset HEAD^ -- somepath/whateverfile
git commit --amend --no-edit

People shouldn’t be attacked, but also ivory tower neighborhoods and the inequality they showcase shouldn’t exist.

I’ve had both forever. It’s been a while, but I remember switching without much issues.

Droid-ify still shows permissions

Maybe exiftool I think they support a few fields for videos.

I have very little doubt that the US is involved in pushing Alberta separatism propaganda for exactly this purpose.

I have stockpiles of styrofoam.

I shower 360 noscope style

I mean, my phone charges at 60W. Granted, it’s not charging 24/7 but 50W is pretty good indeed.

You can hang t-shirts too though

I once thought I was going overboard by protecting my homelab git stuff behind mTLS.

and let’s hope that the login page doesn’t have any vulnerabilities…

Home assistant also supports mTLS.
home assistant is something you’d likely ever want to allow from a handful of trusted devices, so deploying a client certificate on them can make sense.
This way a non-onboarded device doesn’t even get to the html part, it’s denied upstream by a reverse proxy before HA is involved.

what does it make the people that allow it to happen on their watch?

I’d go with traitors, but traitor morons is fine too ig.

I’m a big fan of mutual TLS, which I just do in nginx reverse proxy.
Client certs get installed on trusted devices and then it’s mostly seamless.
Not every app will support it, but I use Firefox as a fallback for stuff that doesn’t, or my VPN.
TBH, I’m just happy homeassistant supports it as that’s the one thing I’d rather be as seamless as possible.
Other things I don’t mind having to connect a VPN for, like jellyfin, which I don’t currently share with others.
For nextcloud I’m currently not running mTLS as it wasn’t supported back then and I had to share some links with some people where I wouldn’t deal with certs. I think mTLS support has been merged since, so if you just use it for devices under your control, or might be viable

Not necessarily since the initial layers don’t have the space to be squished properly, subsequent layers can show the same problem, except they’re too close to the previous layer instead of the bed itself.

That said, the picture didn’t load before but now it does.
With the picture, this looks kinda like wet filament to me where it’ll kinda bubble here and there.
I’ve also spent way too much time hunting down underextrusion what was ultimately just the filament that had a weird undersized diameter like 1.6mm.
Diameter that’s off but consistent through the roll can be compensated for in the slicer, inconsistent diameter not so much.

All good answers so far.
Basically your internet gateway doesn’t support what’s called NAT hairpin, also called NAT loopback.

The DNS solution is better anyway, and that particular setup is called split-horizon DNS, which basically just means your internal DNS requests get different results than ones from outside your network.

Nozzle might also just be too close to the bed.
Mine did a kind of of “tock” sound when it struggled to extrude.

PS: image link seems broken

For one thing, it still has the option for an additional fingerprint lock to open the app.
Sure, my phone itself is locked anyway, usually.
I still like having the second lock built into the app itself for the odd time (however rare) that I hand my unlocked phone to someone.
I know they’re not snooping into my signal messages while I blink or misclick on a notification or whatever.

It may not be a big deal for some/most but I like that feature and I can’t imagine that’s something that needs much upkeep once initially implemented.

I’m sure it’s not the only feature, but it’s one I use often.

What a smooth brain

Signal (but actually Molly)