zrail

Having grown up in a small midwest town in an R&R desert, I think the canonical answer is a liquor license.

I'd expect you to want this

The thing is, I don't want any of that. At least, I don't want any of it to be dynamic. For my purposes the more I can determine at deploy time and make static the better.

K8s is a stack of dozens-to-hundreds of control loops that are built around the idiosyncrasies of a particular distributed key-value store that is only moderately fit for purpose. This is all great fun if you want to learn about it (I did!) and/or if you get to be a user rather than an operator.

Sure! That's the setup I was running before all of this. My problems are likely entirely my own making, tbh, as described in the article.

IME K8s in general and longhorn especially behaved poorly in the face of heterogeneous hardware where the largest node is flaky and has more cores and memory than the rest of the nodes combined.

My point is that, for me, in my setup, with my own idiosyncratic constrains, trying to keep up with Talos + longhorn + fluxcd expended way too many spoons in any given month.

Hey thanks! That's my favorite recent addition.

The host machines resolve a GUA from an ISP-provided prefix like normal. On top of that, I l33t'd my way to a fun ULA prefix. Each host's prefix, the stack network prefixes, and container addresses are deterministically derived from hashes of each component's name.

As of today I haven't made any of the ULA stuff routable, although that was the original impetus for it. Clients see each host's GUA in DNS and generally route traffic through Caddy. Cross-host traffic is almost entirely through Tailscale. I run DNS refreshes at deploy time and hourly, but I haven't dealt with Comcast rotating my PD assignment yet. It's been stable for a couple years so I'm probably due.

Agree! There are a ton of people out there that are happily running k8s on their homelab and there is absolutely nothing wrong with that. I tried it and found it was just too much for me.

I haven't, mostly for personal reasons rather than technical ones.

Hey, author here. This is a piece about moving away from kubernetes and toward something that I can actually maintain as a solo person who has a life outside of k9s. It's not really intended to be "anti-kubernetes", more like "kubernetes really is too hard for my purposes".

IMO the best change that I've made has been to give deterministic IPv6 addresses to every container and then using those for ingress.

I'm curious to hear where y'all think the line is between docker compose with Ruby glue and "Dear friend, you have built a Kubernetes".

    Location: Michigan, US
    Remote: Yes
    Willing to relocate: No
    Technologies: Ruby, Rails, Go, MySQL, PostgreSQL, Redis, Docker, Kubernetes, Finance, Banking
    Résumé/CV: https://www.petekeen.net/resume
    Email: hi@petekeen.net

Mold growth is a moisture problem which can either be because of condensation or because of leaks. I agree with the contractors, properly framing out and insulating the interior would probably help a lot with condensation on the inside of the aluminum, as would double pane windows. Ventilation is also important for stopping mold growth.

"Density of cliches" is a great way of putting it. It's exhausting to write that way and unpleasant to read back in the edit process which is why that kind of thing doesn't happen (often) in human-led pieces. LLMs don't get exhausted.

I think this depends on the construction of the rest of the house. A typical stack built house in the US will have extensive insulation in the exterior walls, but it's paired with a number of different layers intended to expel moisture.

As a retrofit without those things I guess I can see it being problematic.

Does this work? https://imgbox.com/p2O8aADv

I've thought about doing this a couple times but haven't followed through yet. What makes yours different/unique compared to, say, pi?

Nice! I built something along these lines but far more janky. My setup is a clamp-mount mic boom arm and an L-shaped bracket, along with a mic-to-1/4" adapter. Boom clamps to the monitor arm, reaches over the monitor, then the short end of the L is attached to the arm via the adapter. My webcam has a 1/4" screw built in, so that attaches to the long side of the L.

I've been using it for years, works great to get the camera down for calls and back up out of the way when not needed. Only problem is that it's not super stable so I have a small spirit level insert glued to the top of the camera to make adjustments easier.

Edit: somewhat recent photo of my setup, including the webcam: https://imgur.com/a/ip3ff4F

Same. The prompt was essentially, every checkbox in this PLAN.md should be task in SQLite.

Excellent. Tiny affordances like this should be more commonplace, IMO.

I think this probably also helps when truly clueless users drop the link into an agent directly, because then the agent will relay the message to the user.

It's not a new usage by any means. Like almost all slang it originated with Black drag and LGBT+ subcultures and only semi-recently (within the last 10-15 years maybe?) broke containment in the US.

As a verb, "to clock" means something like "to notice" or maybe in this case "to highlight, with specificity".

I feel like I'm way more cynical than most people around here about LLMs but if we accept the parent comment's framing, why can't we just use an LLM to write a throw-away converter to whatever new format is necessary? Yes of course it'll probably be lossy occasionally but the question will be, is that ok for the user doing the conversion?

Sweet, free upgrades!

Edit to be slightly less obtuse: surely you're not implying that a common carrier be allowed to discriminate based on facts about a passenger's body without making reasonable accommodations. Surely you're not implying that obese people not be allowed to fly at all. Surely you're not suggesting that fat people should just remove themselves from society so you don't have to deal with them.

Therefore, obese people should get free upgrades to economy plus or better. Thanks for the idea!

Our house came with one and we upgraded the unit a few years ago. It's very efficient in terms of units of energy consumed, but in my area of the world gas is significantly cheaper than electricity so it ends up being expensive to run.

That said, we will install solar at some point and then it'll be "free" HVAC.

they end up coming up with something equivalent to IPv6

Not just that. Almost every single thing people think up that's "better" is something that was considered and rejected by the IPv6 design process, almost always for well-considered reasons.

A reasonably fair comparison. The ISPs had a much stronger incentive to finish the migration, though, because the 3g spectrum could just get turned around and used for 4g after rollout. IPv6 doesn't really have that strong of an incentive structure now that CGNAT is a well-developed technology.

This proposal is absolutely wild.

Out of curiosity, what makes Home Assistant a pain?

Passkey auth is also available as a first-class option.

Would you be willing to quantify what "mild" means to you, maybe in terms of a USDA zone? There are maps for both US and Europe:

https://planthardiness.ars.usda.gov/pages/map-downloads

https://commons.wikimedia.org/wiki/File:USDA_hardiness_zones...

You already can with nRF52 boards. Presumably they'll add ESP32 support soon too.

https://esphome.io/components/zigbee/

The headscale API is very different than the Tailscale API so if you're automating setting up clients it's not quite drop in. Once a client is up, though, from what I've heard it's seamless.

I think this is mostly a Wireguard thing and not specifically a Tailscale thing. Wireguard does what they call "cryptokey routing" where if you prove you possess a key that the other peer knows, you get the traffic (subject to firewall, allowed IPs list, etc etc). Wireguard stores the most recent address:port that it heard from a particular cryptokey on, but it natively lets peers roam, as long as only one roams at a time.

From what I can tell you're pretty much right. A linux bridge cannot possibly be as efficient or speedy as a dedicated switch asic. OpenWRT has support for a few different hardware switch kernel APIs, but you can't exactly buy one of those on a PCIe card and I've never seen one of those N100-class boards with one instead of a set of i226 ethernet controllers taking most of the PCIe lanes.

Mikrotik sells the CCR2004-1G-2XS-PCIe, which is a fascinating device:

https://mikrotik.com/product/ccr2004_1g_2xs_pcie

It is a full Mikrotik router stripped down to just a board and hung off a PCIe interface. Iirc by default it exposes a virtual gigabit interface to the host and otherwise acts exactly like a CCR2004 running RouterOS.

Doesn't really buy you anything vs a RB5009 unless you can use the pair of 25Gbps ports, but it sure is neat.