organsnyder

This was before Extended Validation was available. I don't remember the exact year, but I know for sure it was before 2007 (it was my dad's business, and he passed away in 2007).

That's not how it used to be, though. It used to be that you had to prove a much higher level of ownership, even for standard, non-"enhanced" certs. There was one time we discovered that the business hadn't had its articles of incorporation renewed in the state, and the validation process by the cert issuer caught it.

I do prefer the current model (the trade-offs are worth it, IMHO), but it wasn't always this way.

Could be a combination of factors:

1. AI agent deletes the primary copy 2. Backup system fails (when did they last test the restoration process?), so they have no copies

> As long as the battery has enough energy to cover the outage the end result is the same.

That is the key—having enough battery to cover an extended outage is very expensive.

My generator can run on natural gas, which is piped to our house and only had one outage in the fourteen years we've lived there (when the gas company replaced lines as part of preventative maintenance). So effectively, we have a redundant electricity source coming into the house. If that was also down, I could also run it on propane or gasoline.

That being said, if I had to pick batteries _or_ a generator, I'd prioritize batteries. We have both, and the batteries cover the majority of outages, while also providing other benefits.

My utility doesn't have a program quite like this, but they do have a peak power rate that incentivizes similar behavior. I have our system configured to charge up to 90% at 12pm, and then consume no grid power until 7pm (peak rate is 1-7pm), or if the battery gets down to 35%.

I also have it configured to charge to 100% if there are any weather watches or warnings. That overrides the time-of-use configuration.

We do also have a generator that I can hook up if the batteries get too low. We have enough battery to get us through the night, but we don't have enough solar to keep up in an outage during the darker months, or if we want to run the A/C.

Bartlet / Hoynes '98!

I wonder how many datacenters bother with those sorts of things anymore, given how many workloads are no longer tied to individual nodes. Seems like it would just be easier to accept that a certain percentage of nodes will be down at any one time, and go through and repair/replace them as needed.

I'm shaking! I'm shaking!

They're different sites, with different goals, run by different people.

Of course you can, but that's not what's implied by the quote.

In addition to microtonality, many instruments (and the human voice) are capable of infinite tuning, and musicians will deviate from the "correct" note (as played by an even-tempered instrument) based on chord structure, voice leading, etc.

> That would be a huge mistake if we expect many more hardware and OS running them efficiently than just iOS and Android.

Is that something we should be engineering for right now?

That's fairly rare. Most companies would use a compatibility layer instead.

I tried it out for a trip yesterday. I wanted to love the app—it has a great retro feel, and an ad-free subscription option—but it gave me weird routes and the audio was extremely stuttery.

Yes, latency is excellent. My ping time to 1.1.1.1 is 6ms on wifi.

I have 5Gbps symmetrical. I love having it, but the biggest use-case has been bragging about it to my colleagues. I haven't even had the full bandwidth available at my desk for a while now (I've had a terrible time terminating cat6a for reliable 10Gbe, so I'm usually on wifi), and it hasn't really bothered me much.

I'm guessing that right now many countries wouldn't like the idea of areas being served solely by an American ISP.

Any evidence of this happening? I imagine that fiber manufacturing is much easier to scale up than chip manufacturing (of course, the devices that attach to the fiber might be a different story).

We built a new garage with an upstairs ADU when I started working from home in 2018. It is indeed a game-changer, and when we no longer need the space we can use it for a rental, guest house, etc.

The best I've come up with is to ask an agent to come up with questions to help get to a focused design. But it still needs me in the loop for that.

So far, the LLMs I've used need problems to be fairly specifically scoped, or they don't produce the correct solution. Scoping problems correctly is a different skill-set than implementation, but it's still a technical skill that is expected from mid-level and higher engineers.

Interesting. I always click through to the regular search instead of waiting for the AI results to load, under the assumption that they'll be even worse (somehow) than normal search. Maybe I should give it a try.

You're always free to purchase a new laptop, though.

It's much more difficult when the ownership of the vehicles isn't centralized.

Workplaces (and other locations) could offer free/reduced-cost charging, with the caveat that V2L is required. They could guarantee that the vehicle will be at a certain charge level at a designated time, and that the vehicle will never go below a threshold (in case an unanticipated trip is required).

This is a question for your doctor.

I'd argue that seriously upending global energy markets (and perhaps the entire economy) is quite a high cost.

Musk definitely gives Dukat vibes.

Exactly. I've lost count of the number of times I've found a brand I liked, only to see quality go downhill after the company tries to scale too quickly, gets bought out, goes public, etc.

I run a k8s cluster in my homelab, with Longhorn providing storage. Except for some extra-large volumes for bulk storage (just movies in Jellyfin right now), everything is replicated three ways. I've had nodes fail to boot up after a power outage (turned out to be a dead CMOS battery) and procrastinated bringing them back up because everything just kept working.

I run a fairly large homelab (probably ~10 nodes when including OPNSense routers, backup NAS at our cottage, etc.), and hardware failures have been incredibly rare, especially compared to what it used to be a couple of decades ago (I had quite a few motherboards fail due to blown capacitors due to the stolen electrolyte formula scandal).

Hardware failures tend to follow a bathtub curve: there are more frequent failures early on due to manufacturing defects, then they become rare until you reach the end of the natural lifespan of the equipment. That is shorter for some components (spinning rust HDDs, fans, CMOS batteries, power supplies in noisy environments), but extremely long for others.