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.
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.
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…
The facets about your father than you find bad are not about being “male”, even as I wager he asserts it to be.
I’m old enough that the vaccine was unavailable, so I got the illness and at least one scar, but my kid was vaccinated and all my peers’ kids are vaccinated so they just won’t know what it’s like.
Seems like some countries think it’s better to keep it around to keep previously sickened people exposed to keep their immune system active to mitigate shingles, but seems like the data in the ‘vaccinate most of the kids’ countries have shown that this doesn’t actually matter, so we might see more countries embrace vaccinating against it.
The NIH director was appointed by Trump, which came with a pretty strong anti-mask, anti-vaxx, and general ‘covid was a hoax’ sort of baggage, so he is unfortunately not that credible.
There is a study that correlates to the ages he specifies, but the conclusion is that the risks inflicted by the vaccine were still lower than the risks of COVID itself even for that age group, but no matter how they sliced it the risks either way for the age group was minimal, neither the vaccinne nor COVID were too risky overall. Pre-vaccine chicken pox was deadlier to kids than COVID was to that age group, and we didn’t consider that to be particularly risky, mostly worth vaccinating due to heading off the chances for shingles later.
In the age group most at risk of COVID-19 vaccine myocarditis (12–29 years), for every 100 000 vaccinated, compared to about four more cases of myocarditis we have 56 fewer hospitalizations, 13.8 admissions to intensive care and 0.6 fewer deaths. Several studies have shown that post vaccine myocarditis/pericarditis are generally short-lasting phenomena with favourable clinically course.
The paper recognizes a 0.004% increase in mild short term myocarditis, with about a 0.05% decrease in hospitalization, 0.014% decrease in intensive care needs, and a 0.0006% decreased chance of death from COVID.
Of course, all this suggests that in that age range, it’s messing with all very low percentages, so it’s pretty much a wash whether they vaccinate or not, statistically speaking. But the vaccine risk is not ‘much higher’ and the severity of the risk is generally low, and seemingly still technically lower risk than COVID itself, but the risk for any of it is kind of down in the noise.
It doesn’t “prevent” but it strongly mitigates how infectious you become and for how long.
Hell, look at the “startup idea” result. So much of absolutely nothing, ironically tossing “zero-fluff” into material that is blatantly only fluff. No wonder execs are creaming themselves…
Next chapter needs to be: “Fucking magnets, how do they work?”
They will require the requester to prove they control the standard http(s) ports, which isn’t possible with any nat.
It won’t work for such users, but also wouldn’t enable any sort of false claims over a shared IP.
If you can get their servers to connect to that IP under your control, you’ve earned it
I’m not exactly sure what you think the specific ask is…
It’s very general, somehow he has the funds to have a maddeningly extravagant wedding, so he can afford to have a tax burden…
It’s vague and doesn’t invite debate over the nature and nuance of his wealth, only that he can somehow pull off a celebration no reasonable person could dream of, including closing off a whole crap ton of Venice to general public use for a whole week. That’s a whole lot of spend that he can casually brush off indicating that in real terms he’s got unreasonable levels of wealth.
It’s not getting down in the details about unrealized gains and leveraging said gains through loopholes and the discussion about what taxable burden might should be associated with unrealized gains of that magnitude, it’s showing a clear example of “he has extravagant financial power, without as high relatively of a financial burden”.
The intelligence agencies contradicted that narrative. The administration hasn’t made a case that it is actually happening, but have just declared it so.
Very much rhymes with declaration that Iraq had WMDs.
As far as evidence goes, it looks like Trump has dragged us into another conflict that we really shouldn’t be in. Which is dissapointing as if there was one small silver lining about Trump was that his rhetoric used to be that we shouldn’t be wasting military resources in middle east conflicts so much.
I’m making a note here: Huge Success
This sounds like a whole lot of convoluted bullshit to use Plex locally and “looking local” through VPN solutions when you could just roll a Jellyfin instance and do things a more straightforward way…
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.