https://en.wikipedia.org/wiki/Reinhold_Messner

As for how this relates to audio compression, in particular in the context of 2012. you are making a tradeoff of storage size and decompression cost. Maybe that doesn't matter to you, but maybe it either did in 2012 or still does.

There's a variety of roles. Security, electricians, HVAC engineers, generally some type of site foreman-ask role, logistics (depending on the size of the place), and technicians (for a lack of a better word, feels like every place calls them something different). There's a variety of roles that often float between sites or oversee many sites, depending again on the scale of the place. AWS is huge. Bigger than you're imagining, so there's quite a few levels deep and include real estate folks as well as construction roles. If you go and look at job postings, you'll even see roles for nuclear engineers at some companies.

But generally what you're talking about here are what I'm calling the technicians. They're responsible for wheeling racks into place (depending on the company they may also be responsible for unloading the trucks). Cabling is nearly always outsourced these days (though not the design of the cables), so rolling a rack into place generally involves securing it to the floor and connecting power, data, and more often than not now-a-days liquid cooling.

The other part of their job is "troubleshooting" failed hardware. Again, really depends on the company. Big big shops have "dumbed down" troubleshooting as much as they can - for a lot of reasons. You don't have to pay folks as much because they're thinking and doing less, the more time they spend troubleshooting the longer the server is offline, and if there's no troubleshooting there's not much for them to screw up. I'm sure there are some great places to be a tech where you get to rip apart servers and bust out the multimeter, that to my understanding is not how the hyperscalers who actually hyper-scale do it.

There's some cleaning, parts management, destroying broken hard drives, shoveling snow off the roof (no lie), and a variety of other odd tasks.

If you ever have the opportunity to check out one of those places it can be a riot and a real eye opener. Depends again on the company though, some of those places have insane security (metal detectors, badge+pin, turnstile door procedures) which make visits super un-fun if they're even allowed outside of legit business reasons. Other companies... well I'm glad that's not where I store my data.

Back "in the day" (2005 give or take a handful of years) techs would often write their own automation and even build some simple services.

And yes, the jobs don't pay particularly well depending upon what it is. Electricians and such command decent wages, but the security guards and techs don't make crazy amounts. I think folks doing contract cabling can come out ahead.

Anyhow, SWEs are wildly insulated from the realities of what things look like on the ground. Maybe that's a good thing, IDK.

https://www.science.org/doi/10.1126/sciadv.adx4298

Basically newer modeling has shown a stronger weakening of the system. Lots of uncertainty, but 1/3rd loss by 2100. There's a lot of unknowns with feedback loops and tipping points where the whole thing might collapse if a threshold is crossed.

Comments URL: https://news.ycombinator.com/item?id=47316130

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47240757

Points: 3

# Comments: 1

Since iOS of a couple of versions ago, you can trigger color filters on and off from shortcuts, and get a similar behaviour, but it isn't perfect and sometimes glitches. I do this so my photos app and a few others are in color, but the rest are in grey scale.

TLS 1.3 version in the record header is 3.1 (that used by TLS 1.0), and later in the client version is 3.3 (that used by TLS 1.2). Neither is correct, they should be 3.4, or 4.0 or something incrementally larger than 3.1 and 3.3.

This number basically corresponds to the SSL 3.x branch from which TLS descended from. There's a good website which visually explains this:

https://tls13.xargs.org/#client-hello/annotated

As for if someone is correct or whatever for calling out TLS 1.x as SSL 3.(x+1) IDK how much it really matters. Maybe they're correct in some nerdy way, like I could have called Solaris 3 as SunOS6 and maybe there were some artifacts in the OS to justify my feelings about that. It's certainly more proper to call things by their marketing name, but it's also interesting to note on they behave on the wire.

When the bad guys want to DDoS the personal blog website they don’t go and figure out the correct amount they need to send to fill up that pipe/tube that directly connects the personal blog website, they just throw roughly one metric fton at it. This causes the pipes/tubes before the personal blog website to fill up too, and has the effect of disrupting all the other pipes/tubes downstream.

The result is your hosting provider is pissed because their infrastructure just got pummeled, or if you’re hosting that on your home/business ISP they also are pissed. In both cases they probably want to fire you now.

These broad numbers games feels like rationalizing a decision today. Maybe it’s true for a particular locale (I don’t live in the Bay Area), but these articles feel like they’re painting with too broad of a brush given I can’t maths out a negative for my situation.

Comments URL: https://news.ycombinator.com/item?id=44251863

Points: 9

# Comments: 5

https://lwn.net/Articles/961978/

tl;dr: The Linux kernel team view all bugs as a possible security issue. The CVE assignment teams tries to minimize the number of Kernel CVEs because corproate policies mandate fixing CVEs in 30/90 days. There's a lot of politics.

https://climatereanalyzer.org/clim/sst_daily/

\0