Baconeggncheese*

I am aware but going from winter layers and materials to summer there's 1/8" variation at minimum and it's enough that it almost causes a tick to readjust. And yeah the dress belt also has its own situations.

Honestly I expected the ratcheting/clamping both to fail somehow and for me to go "oh I get why people don't get these"... That did not happen. At this point for me it's not "find an argument for why this over traditional" its "what does traditional offer that's better than this".

Yeah I wanna know more about the watercraft

I just dedicated some cabinet space to store them with lids on. Takes up more space but never have this issue.

Just wanted to add a clarification that both editions are offered currently.

Leather belts tend to wear out at the holes and you're always playing with too tight too loose.

Work dress/work belt I went with a Ratcheting one for pretty cheap on Amazon. Its like new 3y later. Def fake/cheap leather though.

For everyday, I got a nylon (?) Belt with a plastic latch clasp. It's been 6y, like new. And it doesn't set off metal detectors.

the old crowd is still going strong and have been proven largely correct because what they/we were really against was going from a "you own this software" model to a "perpetual licensing" model with price hikes, lock-in, and everything becoming a service.

it's not completely enshittified, there are lots of great cloud-based services. some long-term, some at various stages of the enshittification curve.

same with AI. it doesn't all suck, and it won't all suck. but a lot/most of it does and will absolutely suck and it will enshittify many things.

Android does this too (ETA: by default). There's a history. You can set Signal to not display message content in notifications.

So remember that it's one core (physical) acting as if it was 2 (virtual). Each of these vCores could be assigned to separate workloads on a server. But because it's ultimately one core, threadA could possibly access data in threadB. If A was a different entity than B, then entity A could access entity B's data.

It's more that CPU architecture is insecure in general.

But so is literally everything when you go down the deep dark rabbit hole of all the tech we use. Meltdown, Spectre, rowhammer, VMScape. The one where they can figure out your password from the sound of your keyboard while you're on a zoom call.

Switches 3 and 4 are single points of failure. The other 2 & 5 are completely redundant unnecessary.

You can just use 2 switches total, cross-connect each to upstream, and do vLANs/subnets to isolate the traffic downstream.

Edit: if you really wanna do physical separation and you want redundancy you'd want to connect 2&5 to both routers.

Honestly tho textbook network with that many nodes for so few devices is already overkill for home, so doing that many switches is just... Idk man, doing full stack troubleshooting for an hour while everyone's just trying to watch a movie is gonna do more hatm than good.

Whoever implements this should probably spin up a ticketing system for the house.

ELIsysadmin?

You mention a node sparse neighborhood. Nodes of what platform?

Im gathering that there is a mesh network being slowly built? I have so many questions and concerns. What are we sharing and isn it bridged to the web and how are we isolating and securing.

A link further down the rabbit hole would be fine.

EDIT I'm an idiot and realized from the community name this is meshtastic. Rabbit hole here I come.

Accurate

Application: full of itself; just look at it; leaking out of its constraints.
Presentation: not happy; has to talk to the app.
Session: chillin; don't start nothin, won't be nothin.
Transport: ready for whatever comes its way.
Network: acting up as usual.
Data Link: Hidden but watching, well-behaved, compliant.
Physical: draping out of the rack

Honestly it took me a while to convince myself this wasn't a painting. At one stage I wondered if it was a Wes Anderson set.

Just price out S3 compatible storage and use backup software that can encrypt. Then it doesn't matter who holds it.

Wasabi is reputable and has fair pricing. iDrive is well priced.

I'm still sending to B2 until the price actually changes for me.

I personally use Duplicati (and yes I've tested restores).

Its time away from your employers needs.

How you choose to spend it is ykur call.

Every non-empty flask contains both soup and liquor until you take a sip.

The actual line from the film:

No more colored restrooms. No more white restrooms. Just plain old toilets. Go wherever you damn well please. Preferably closer to your desk. Here at NASA we all pee the same color.

ETA: you can truncate a lot of scenes to change their meaning. Remember that Braveheart speech that ended with the lines "Fight and you may die, run and you'll live"? What a terrible way to inspire your troops.

It is not derogatory. The word means:

"... or disfigure, especially by cutting off tissue or body parts."

from Latin mutilātus (past participle of mutilāre “to cut off, maim”)

keys tend to be organized (that's a horrible word for whatt he registry is lol) in a handful of locations depending on context. so those chrome keys are next to the other chrome keys. in enterprise we mod that area pretty often.

the 2 was to discover a new key are:

1. reg watcher that takes a baseline, then you install soemething, and you see the diff.
2. in the case of no new key has been added (like for this new setting), most softwares have support articles aimed at Enterprise Admins who need to control deployments granularly. So the regkeys tend to be available.

Sometimes some dev figures it out, sometimes word spreads from the devs themselves on Discord/etc. Sometimes if you contact Support they have that workaround (after escalating to engineer). Not that you can easily get to Google Engineers, but you have a much better track with say a paid Workspace account.

It's a FT job though to maintain a set of controlled software in an enterprise environment. Constant fiddling/tweaking. SOmetimes it's a RegKey, sometimes a GPO setting, sometimes you're modding a config file in AppData, or adding some lines to a Logon Script. And a lot of the info spreads by word of mouth still and to really answer your question - sometimes, no one knows where the hell it came from but after days of searching, you're happy some random forum post finally worked and you hope to never have to touch it again. Then you close your ticket and move on to the next one.

I don't miss it lol