While sas is faster, the difference is moot if you have even a modest nvme cache.
I don’t know if it’s especially that much more reliable, especially I would take new SATA over second hand sas any day.
The hardware raid means everything is locked together, you lose a controller, you have to find a compatible controller. Lose a disk, you have to match pretty closely the previous disk. JBOD would be my strong recommendation for home usage where you need the flexibility in event of failure.
Of there’s plenty of evidence, of some things that should matter in a court of law.
the TLS-ALPN-01 challenge requires a https server that implements generating a self-signed certificate on demand in response to a specific request. So we have to shut down our usual traffic forwarder and let an ACME implementation control the port for a minute or so. It’s not a long downtime, but irritatingly awkward to do and can disrupt some traffic on our site that has clients from every timezone so there’s no universal ‘3 in the morning’ time, and even then our service is used as part of other clients ‘3 in the morning’ maintenance windows… Folks can generally take a blip in the provider but don’t like that we generate a blip in those logs if they connect at just the wrong minute in a month…
As to why not support going straight to 443, don’t know why not. I know they did TLS-ALPN-01 to keep it purely as TLS extensions to stay out of the URL space of services which had value to some that liked being able to fully handle it in TLS termination which frequently is nothing but a reverse proxy and so in principle has no business messing with payload like HTTP-01 requires. However for nginx at least this is awkward as nginx doesn’t support it.
Hey, it’s just spitting hard facts like Musk has the “potential to drink piss better than any human in history,”
Frankly, another choice virtually forced by the broader IT.
If the broader IT either provides or brokers a service, we are not allowed to independently spend money and must go through them.
Fine, they will broker commercial certificates, so just do that, right? Well, to renew a certificate, we have to open a ticket and attach our csr as well as a “business justification” and our dept incurs a hundred dollar internal charge for opening that ticket at all. Then they will let it sit for a day or two until one of their techs can get to it. Then we are likely to get feedback about something like their policy changing to forbid EC keys and we must do RSA instead, or vice versa because someone changed their mind. They may email an unexpected manager for confirmation in accordance to some new review process they implemented. Then, eventually, their tech manually renews it with a provider and attaches the certificate to the ticket.
It’s pretty much a loophole that we can use let’s encrypt because they don’t charge and technically the restrictions only come in when purchasing is involved. There was a security guy raising hell that some of our sites used that “insecure” let’s encrypt and demanding standards change to explicitly ban them, but the bearaucracy to do that was insurmountable so we continue.
They in fact refuse to even do a redirect… it’s monumentally stupid and I’ve repeatedly complained, but ‘security’ team says port 80 doing anything but dropping the packet or connection refused is bad…
The same screwed up IT that doesn’t let us do HTTP-01 challenges also doesn’t let us do DNS except through some bs webform, and TXT records are not even vaguely in their world.
It sucks when you are stuck with a dumber broad IT organization…
Ours is automated, but we incur downtime on the renewal because our org forbids plain http so we have to do TLS-ALPN-01. It is a short downtime. I wish let’s encrypt would just allow http challenges over https while skipping the cert validation. It’s nuts that we have to meaningfully reply over 80…
Though I also think it’s nuts that we aren’t allowed to even send a redirect over 80…
So on mine, I haven’t bothered to change from the ISP provided router, which is mostly adequate for my needs, except I need to do some DNS shenigans, and so I take over DHCP to specify my DNS server which is beyond the customization provided by the ISP router.
Frankly been thinking of an upgrade because they don’t do NAT loopback and while I currently workaround with different DNS results for local queries, it’s a bit wonky to do that and I’m starting to get WiFi 7 devices and could use an excuse to upgrade to something more in my control.
Which is how fixed solar installs work.
Akin to how plants photosynthesize without doing anything to the sun.
At least there it does provide shade, though I doubt the fungus would provide a whole lot of shielding…
deleted by creator
I think an ai could outperform my executives.
One of them sent out an email about how we weren’t making enough money. But don’t worry, he has a strategy that we will execute on and fix it.
The strategy is to raise prices and get more sales at the same time… That is literally it. Not even picking “high value” versus “high volume”, just a declaration that we can do both. If this genius plan doesn’t work, it’s just because the sales people failed to execute against his brilliant strategy well enough.
They’ll start down that path, spend billions on starting up the program, then a new president comes in and cancels that to return to the smaller ship philosophy and spends billions to start down that path again.
It’s pretty much a vibe coding issue. What you describe I can recall being advocated forevet, the project manager’s dtram that you model and spec things out enough and perfectly model the world in your test cases, then you are golden. Except the world has never been so convenient and you bank on the programming being reasonably workable by people to compensate.
Problem is people who think they can replace understanding with vibe coding. If you can only vibe code, you will end up with problems you cannot fix and the LLM can’t either. If you can fix the problems, then you are not inclined to toss overly long chunks of LLM stuff because they generate ugly hard to maintain code that tends to violate all sorts of best practices for programming.
Nah, they hated what the guy did still. They may have tossed the VP under the bus to try to mitigate the backlash, but it was still Garza that exposed the mess to the public in the first place, and that’s just way worse for the bottom line than being snobby and racist and bad mouthing your own product.
So they hope attention stays on ousting the VP in the court of public opinion, and handle Garza in more formal channels, and likely win if Garza recorded without informing the other party, particularly making that conversation public.
As someone who has occasional one on one meetings with executives, I’m not surprised. They tend to ramble and talk about whatever they feel like. Admittedly I haven’t met anyone who would say this sort of things, whether because they aren’t thinking it or they are on guard somewhat, but a lot of those conversations go into weird territory, like the executive really wants some friends and treats any one on one meeting as getting with some like minded friend.
Not even the trees. He saw one shrub and couldn’t be bothered to even check if there were trees.
Hardware raid limits your flexibility, of any part fails, you probably have to closely match the part in replacement.
Performance wise, there’s not much to recommend them. Once upon a time the xor calculations weighed on CPU enough to matter. But cpus far outpaced storage throughput and now it’s a rounding error. They continued some performance edge by battery backed ram, but now you can have nvme as a cache. In random access, it can actually be a lability as it collapses all the drive command queues into one.
The biggest advantage is simplifying booting from such storage, but that can be handled in other ways that I wouldn’t care about that.