Kessler and/or Fermi…

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

It’s likely not the cause but a symptom or collateral damage.
It’s probably just one of the things that no longer works when it disconnects.

Imagine you’re the guy working

Idk, An employee entering whatever gender toilets to clean it isn’t gonna be seen as creepy imho, unless they’re being actively creepy, like by recording videos with creepers’ glasses. I mean, menployees clean women’s toilet all the time and womenployees also clean men toilets.

I can’t believe many if any business is currently paying gender-specific cleaners for gendered toilets. An employee would just grab that yellow rolling cleaning cart and deal with the thing and move on. It’s a scenario that happens literally everyday everywhere unless the place doesn’t clean their toilets.

Since the instance itself is dead, federation won’t work. Basically the way it works now is it needs to be removed from each individual instance.
An admin could also decide to lock it instead of deleting it but there’s like 3 posts in it.

It’ll likely hold a liquid warm for longer than the battery-thing too. ¯\_(ツ)_/¯

A fire is way more expensive though.
If you need to keep something hot, just get something like a zohirushi mug.
It’s so well insulated that I have to dump an ice cube in it otherwise it’s stays too hot for too long.
No batteries, no gimmick. Mine is 11 years and still kicking.

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.

We had to enable attack mode on sjw because the poor server was getting hammered by bots, which breaks apps. It had nothing to do with your device or Google, it was unusable most of the afternoon until we enabled the anti bot verification thing.

Not a pro, but I usually add cheese off the heat because too much heat can make it separate into squishy gloops and watery whey.

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

Also, you can check the currently blocked accounts here:
https://sh.itjust.works/settings
(Click the blocks tab) You can add add users from there, although I usually do it from their profile page.

I don’t know about connect, but you can block an account in your settings in the web UI easily enough. That should then also be blocked whenever using whatever app.
Just hit the block button from that user profile.

An out-of-band means of communication is indeed very useful to have.
We have a matrix channel, which is linked in the instance sidebar after the rules.

Here: https://matrix.to/#/#sh.itjust.works:matrix.org

Yep, the infamous “Starlight Tours”.
Every officer involved in any of this should be fired on the spot, then also fired again but from a cannon.

In the 90s, battlenet was amazing for its time.
Back then, it wasn’t a store or a launcher though, it was a mix of chat channels, game lobbies before matchmaking was a thing.

Everything Blizzard has fallen from grace by so much that it’s hard to reconcile old Blizzard with whatever shit they’re now shoveling.

Old Blizzard was innovative back then, but even that is now tainted by the disgusting way women who worked there were treated.

I don’t know this particular individual, but this whole premise is like hiring Oracle to fix your PR team.