Shared IPv4 addresses are not to deter hosting but because there aren’t enough v4 addresses to go around. Most ISPs will happily give you an entire block of persistent IPv6 addresses but won’t give you a v4 because of address space exhaustion.

To quote that same document:

Figure 5 looks at the average temperatures for different age groups. The distributions are in sync with Figure 4 showing a mostly flat failure rate at mid-range temperatures and a modest increase at the low end of the temperature distribution. What stands out are the 3 and 4-year old drives, where the trend for higher failures with higher temperature is much more constant and also more pronounced.

That’s what I referred to. I don’t see a total age distribution for their HDDs so I have no idea if they simply didn’t have many HDDs in the three-to-four-years range, which would explain how they didn’t see a correlation in the total population. However, they do show a correlation between high temperatures and AFR for drives after more than three years of usage.

My best guess is that HDDs wear out slightly faster at temperatures above 35-40 °C so if your HDD is going to die of an age-related problem it’s going to die a bit sooner if it’s hot. (Also notice that we’re talking average temperature so the peak temperatures might have been much higher).

In a home server where the HDDs spend most of their time idling (probably even below Google’s “low” usage bracket) you probably won’t see a difference within the expected lifespan of the HDD. Still, a correlation does exist and it might be prudent to have some HDD cooling if temps exceed 40 °C regularly.

Hard drives don’t really like high temperatures for extended periods of time. Google did some research on this way back when. Failure rates start going up at an average temperature of 35 °C and become significantly higher if the HDD is operated beyond 40°C for much of its life. That’s HDD temperature, not ambient.

The same applies to low temperatures. The ideal temperature range seems to be between 20 °C and 35 °C.

Mind you, we’re talking “going from a 5% AFR to a 15% AFR for drives that saw constant heavy use in a datacenter for three years”. Your regular home server with a modest I/O load is probably going to see much less in terms of HDD wear. Still, heat amplifies that wear.

I’m not too concerned myself despite the fact that my server’s HDD temps are all somewhere between 41 and 44. At 30 °C ambient there’s not much better I can do and the HDDs spend most of their time idling anyway.

Given the usual quality of BIOS/UEFI option descriptions it’s remarkably close to being sensible. I would’ve expected something like “enables limiting CPUID maximum value”.

Wasn’t there a Dark Age after Bronze? The one where everyone was scowling the whole time and the stories were so tryhard edgy you could use a typical Youngblood issue as a letter opener?

(Basically the “pouches” era the sibling comments talk about. Rob Liefeld’s contributions to fashion will never be forgotten.)

Mind you, Highlander II would’ve made more sense as a non-Highlander movie that just revolves around space aliens dealing with Earth having a planetary shield now. As a sequel to Highlander its premise was really weird.

Conception begins at meiosis. If you don’t want to procreate, don’t produce ova/sperm. Produce a million sperm cells and only make one child? Off to death row with you, mass murderer!

Of course you wouldn’t use an existing database engine as the foundation of a new database engine. But you would use an existing database engine as the foundation of an ERP software, which is a vastly different use case even if the software does spend a lot of time dealing with data.

If I want to build an application I don’t want to reimplement everything. That’s what middleware is for. The use case of my application is most likely not to speak a certain protocol; the protocol is just the means to what I actually want to do. There’s no reason for me to roll my own implementation from scratch and keep up with current developments except if I’m unhappy with all current implementations of that protocol.

Of course one can overdo it with middleware (the JS world is rife with this) but implementing a communication protocol is one of the classic cases where it makes sense.

Besides, “there are only two sexes” is rather obviously inaccurate. While intersex people aren’t terribly common, they do exist and are well-documented – as are the genetic reasons for why they’re intersex. XX men and XY women are also a thing. Genetics are inherently messy.

But acknowledging all that would mean having to admit that sex is a complex matter and can’t be handled with simple statements like “the one you were born with is the one you should have”. It’s easier to just pretend intersex people don’t exist.

Yeah, the 13 feels a lot more solid. The 16 pays a certain price for its enhanced configurability. Honestly, though, a full-size touchpad module would go a long way to fixing that. The two spacers next to the keyboard look fine (if the keyboard is centered) but the touchpad spacers look less great.

I have a Framework 16. Is it as well-built, efficient, or quiet as a MacBook Pro? Nope. But if something breaks I can easily replace it, and I can upgrade it without having to throw everything away. Also, hot-swappable ports. That’s nice too.

It’s all about trade-offs in the end.

I know I sorted by feed by Top 6 Hours but that doesn’t mean I expect six hours worth of text in a single image. Did they copy and paste three different job postings together? Did they use a LLM that had its stop token configured incorrectly? Is it an attempt at weeding out people who object to having their time wasted by corporate bullshit?

We may never know. What we do know is that this wall of text has more red flags than a Chinese military parade.

Run a fairly large LLM on your CPU so you can get the finest of questionable problem solving at a speed fast enough to be workable but slow enough to be highly annoying.

This has the added benefit of filling dozens of gigabytes of storage that you probably didn’t know what to do with anyway.

That’s why I’ll make damn sure they’ll make that second branch first.

Mind you, the most likely result is that I’ll still see branches with 50+ commits with meaningless names because nobody ever rebases anything.

I’m kinda planning on teaching my team how to use interactive rebases to clean the history before a merge request.

The first thing they’ll learn is to make a temporary second branch so they can just toss their borked one if they screw up. I’m not going to deal with their git issues for them.

That does make encryption was less appealing to me. On one of my machines / and /home are on different drives and parts of ~ are on yet another one.

I consider the ability to mount file systems in random folders or to replace directories with symlinks at will to be absolutely core features of unixoid systems. If the current encryption toolset can’t easily facilitate that then it’s not quite RTM for my use case.

If you use a .local domain, your device MUST ask the mDNS address (224.0.0.251 or FF02::FB) and MAY ask another DNS provider. Successful resolution without mDNS is not an intended feature but something that just happens to work sometimes. There’s a reason why the user interfaces of devices like Ubiquiti gateways warn against assigning a name ending in .local to any device.

I personally have all of my locally-assigned names end with .lan, although I’m considering switching to a sub-subdomain of a domain I own (so instead of mycomputer.lan I’d have mycomputer.home.mydomain.tld). That would make the names much longer but would protect me against some asshat buying .lan as a new gTLD.

It is a well-designed system font. Say what you will about Microsoft but they do know how to make a good font or two.

I remember a friend of mine once ordering a Double Triple Whopper and being annoyed that Burger King’s definition of “double” is “with one extra patty”. So he had to order a Double Double Double Triple Whopper to get the desired result.

They delivered the thing to our table together with a knife and fork. I guess ordering an unholy totem pole of meat like that gets you table service at a BK.

The other thing that was notable about it was that the three "Double"s only added three patties to the burger and nothing else. As a result this caricature of a burger was now 80% overcooked ground beef and extremely dry.

He ate half of it. We took the other half home, put it in the microwave and drowned it in ketchup, which greatly increased it’s edibility. It still sucked, though.

You are insanely naive for saying this. If you’d used non-corporate email servers, like the much smaller email providers out there (which are basically extinct at this point) you’d know just how wrong this actually is. Most smaller email providers out there are blocked or limited by the big ones and the ones that are blocked your mail will never reach the inboxes of people on the big servers, not even the spam folders on those servers. They won’t bounce it back to you either, so it’ll just go into the void.

Most email these days is used primarily by the all mighty trinity: Gmail, Outlook, and Yahoo, and a Few on Hotmail and AOL and while there are a few smaller companies out there like Proton, when it comes to something that isn’t a company or is self-hosted you can expect a lot of problems with domains being blacklisted, IPs being blacklisted, or both. And it’s actually much worse than defederation.

I’ve been using a self-administered mail server (running on a root server at a major hosting provider) as my main email provider for well over a decade. I think I’ve encountered one website where that actually led to issues. Heck, the server once got on Spamhaus’s bad side for a week and once we were off the list everything was back to normal.

Self-hosted mail works very well one you’ve jumped through all of the appropriate hoops (DKIM, SPF, etc.). Sure, running a mail server out of your bedroom probably won’t work very well but if you’re with any kind of reputable hosting provider you should be fine.

You’re beginning to realize why the decision to limit spam and illegal shit was chosen over catering to the people who want the whole federated world instead of what they’re allowed access to. Ultimately it is better for everyone if the depraved shit and spam gets blocked, than it is for the people who want the whole world to have their way. If you want the world, go to Nostr, you’ll learn why most people do not want the world.

The problem is that defederation leads to confusing situations. Being told about a response to your post/comment/toot and then finding nothing when you look is bad UX. Better UX would be a notice that what you’re looking for comes from a defederated instance and can’t be viewed – but that’s obviously impossible because your instance doesn’t even know anything is there.

Not wanting all the content on your instance is perfectly reasonable. But the way defederation works exposes details of the underlying technology to the user in a way many users don’t want to have to deal with, serving as an impediment to growing the fediverse.

It’s not easy to keep unwanted stuff off your instance while also being user-friendly about it. That’s why I called it tricky.