Yes, it does. As far as water is concerned, air conditioners are open loop. Air conditioners make water from condensation forming on the inside (cool) coils. Modern window air conditioners then splash that water on the outside hot coils, to benefit from evaporative cooling. I haven't looked into the details about data center water usage, but I would guess the cited usage is from evaporative cooling.
The real problem is that people need to not forget in a few short years. This is exactly what the Republican party has become, completely. You can find quotes from like half of Republican senators before they were on the Grump train, saying how if they let this guy take over the party they were done for. And yet one by one they fell in line, and here we are - trashed or outright destroyed institutions, smashed economy, pointless forever war, our traditional allies moving on to a world in which we're not the global leader, pathetic response to 21st century industrial competition, etc.
His first term should have been widely recognized as the abjectly terrible leadership it was (dividership, really), but Covid was one hell of an excuse - and if there is one thing Grump is actually good at, it's making excuses. So instead four years later it was forgotten about because of the price of eggs, or her laugh, or the woke, or Palestine, or who really knows. Let's not make that mistake again!
Sure. The genocide has also been made so much worse, despite it being a point of criticism again Democrats.
There is a deeper point to my comment - the damage caused by Republicans often circularly benefits them, and isn't so easy to fix. If we have a "blue wave" now, but oil prices stay high as the strategic damage of giving the Strait to Iran can't simply be undone as easily as it was done, then voters need to remember this in a short 2/4/6 years rather than falling for media campaigns attributing the high prices to the future incumbents.
(Note I'm not coming from a partisan perspective here. I personally am a centrist libertarian! I was both-sidesing up to 2020 or so, but at this point it's only responsible to acknowledge that the Republican party has completely jumped the shark. And as much as the government is frustrating - when it's simply eliminated this doesn't make things more free, rather it leaves a power vacuum that often results in things become less free - ie corporate government).
> That ain't gonna fly - you're going to have engineering requirements for a 100' span wither it's a shade structure or a solar panel
Bingo. "cheap shade" is doing a lot of work. Typical for this kind of drive by "I've thought about it for 5 minutes but the people who worked on this project must be stupid".
Looking at cahsr it is clear that some of the people in charge of infra in California are stupid. They made bad decisions and now I question the new ones they make.
Re names, I like "homeprod". The main goal isn't to experiment and learn, and you're not scrapping to get a pair of Cisco 2501's to study for your CCNA. Rather the main goal is providing services that support your family's larger existence, independent of the surveillance industry - the tinkering is an (unfortunately necessary) side effect.
This is an underestimated part of operating IT infrastructure at home. Something a lot of homelab builders miss. They have a homelab that mixes in the same environment and same equipment the role of delivering standard services for the house and family, with the role of experimenting and toying around.
Everyone who builds this should really have "homeprod" and "homelab". And when the experiments and tests inevitably lead to an outage, the movie streaming or photo storage or home control parts don't die with it.
I very much like how the name "homeprod" contrasts against "homelab."
But I'm not as convinced as the article's author that "NAS" is outdated as a separate concept, just that as new people learn more about networking they rediscover why just having storage on in its own box can be a good setup. And when new people are brand new, having everything on one box is conceptually simpler, though not always optimal.
I think, in the family/household context, I like the names:
Homelab: the box/cluster you use to experiment and test new stuff.
Homeprod: the box/cluster you use to deploy stable services for family. Runs only things that have graduated from at least a yearlong successful deployment or so on homelab.
Homebase: the box/cluster you use to make ZFS pools and databases available to both homelab and homeprod (on the same network or overlay network). Basically a NAS in the older sense of the word, before homelabs started expanding its scope in casual use.
Famadmin: the sysadmin for the family (i.e. "you" in the three items above). The person to whom, as you say, "providing services that support your family's larger existence, independent of the surveillance industry," is a matter of deep principle. And well put, BTW.
Putting aside the awesomeness of the term homebase, what exactly differentiates the base from the prod? Aren't those ZFS pools just production? Or something like an MQTT broker that supports home automation - you're likely running experimental devices/services over that as well, right? And to the extent that experimental MQTT or NAS traffic could inadvertently disrupt the production services, you could separate those out if you really cared. But that would still just be lab and prod.
Maybe the division is more apparent if you're using containers, and/or have more of a social group to communicate support levels to? Personally I'm just using NixOS and am still at the stage of "I'm going to reboot the router now, it might take ten minutes or it might take days" [0]
If we don't need this distinction, then perhaps "homebase" could actually make more sense than "homeprod" ? Slightly different connotations, less putting on a show for lots of people but more homey like for a small family?
[0] from a technical perspective I'd love to separate the router out onto its own machine, but I want fast wireguard/openvpn/TOR/etc so it's a VM on a larger machine and I'm not really looking to expand my power consumption footprint to another large machine. I suppose I could split it out to two routers, one with straight NAT+wireguard and one with openvpn/TOR/etc, then the main could run on its own low-power box.
My homebase has the around 30TB usable storage, but the only workloads I've found really need to run on the same machine (rather than the same local network) are media transcoding for Jellyfin and ML classification of footage in frigate. With those two happening, and with ZFS (appropriately) using a majority of the RAM as a cache, it makes sense to put the rest of services on another machine.
My prod (now homeprod, thanks for the name!) has no HDDs, just SSDs. It's a proxmox cluster that runs opnsense in a VM for the whole network, Home Assistant also in a VM[1], and most other services in containers. In the age of expensive storage, it has just enough SSD space for VMs and containers. VM backups live on homebase, except for opnsense which also needs a backup on the same machine (same machine, not just same cluster) if the network goes down.
So my conceptual distinction is mostly that the only services/containers I put on homebase are doing work that really benefits being that close to the data. Oh, and I'm in the jolly position of needing to replace the hard drives this or next year. Yaaaaay.
My homelab is currently a cluster of 4GB Pis that I had lying around from before even the Raspberry Pi shortage. Whenever I upgrade my Framework 13 mainboard, I'll probably use the old one as a homelab instead of the Pis.
[1]: Home Assistant's plug-ins are themselves containers, so it's a good idea to give it either a VM or its own machine.
I was just naming general concepts, or describing on how one thinks of a service. It seems like you're using the terms as specific labels for a logical group of machines (eg a proxmox cluster), so I understand the need for a third name there for the specific hardware that's providing the common services.
Absolutely, I was running the server on my main desktop before this, and it was super stressful. One of the main drivers was to move things to something more stable. NGL, I still experimenton it though...
Honestly telling your kid going off to college (or elsewhere) "you have to take everything from you care about, the rest is going to go away" seems like a good way to stunt their independence. The natural reaction would be to take as much as they can of their current life, which is then going to be a burden preventing them from growing into a new life.
When you put it this way, it is very anxiety inducing and I understand that. What this is helping me realize is that my childhood, and our lives of our children were different than many of the commenters, not necessarily better or worse.
As children, my siblings and I didn't have a lot of stuff, and our family didn't have a lot of stuff either. It certainly wasn't our intent to traumatize and stunt our children and this doesn't seem to be the case. I will certainly ask them.
I really wish articles like this wouldn't anchor around this refrain of "... while their wealth increased by $XXX". It's a staple of tax law that you're only taxed when income is actually realized, and there are a few glaring loopholes that allow people to avoid realizing capital gains. At the very least, things should be changed such that taking a loan against an asset beyond its basis is considered a realization of income - similar to how if you take a loan against your IRA it is considered a distribution.
But we already knew all that! We don't need numbers calculating out infinitesimally small fictitious "tax rates" (for a tax regime that doesn't actually exist) to illustrate it. Unless someone is actively selling the stock they own, they are not paying any income tax on its value, period end of story.
And so rather it feels like a wasted analysis to keep focusing on the value of zero divided by $big_number, when there are going to be far more interesting things like exactly what income did they realize, and what type of expenses did they use to offset it, what amounts did they actually pay tax on, and so on. Because capital gains deferral is not the only way the tax code skews towards the rich by far, yet it's currently using up all the air in the room.
I like the article, but I'd say it has left out descriptions of those people who weren't in the social Matrices it described (either because they didn't want to be, like "one family who had moved out of the West End into an aging lower-middle-class town" or because they couldn't like those lower orders in "volunteer work is part of what separates them from the lower orders".
In fact I'd say that angst from this type of person (I consider myself one) is a good chunk vocalizing concerns about "a world without work". "Going your own way" is a large part of the American psyche, so what happens in a world where there is not work that needs to be done, which had been laying out straightforward paths for "your own way" ?
I'm personally not feeling too much of this angst, being both happy working on the kinds of physical things that aren't going to be automated away any time soon, and also having the engineering knowledge/skills to effectively use LLMs and benefit from the automation. But I'm also not looking so far into the future as to worry about those endeavors becoming trite.
Do you feel like you have much agency in the economic and political systems that rule our lives? The problem does indeed always come down to humans, but the specific humans with the most agency are generally quite eager to take away the agency of everyone else to increase their own share. And by the time they themselves are actually affected, it's generally too late.
Right on! It's always frustrating reading articles framed in terms of "security breaches" and "dark web", invariably doing hand waving at unspecified harm, when the real threat actor for pretty much everybody is the "above board" surveillance industry. Random people who buy this info outside the law can't really hurt me - it's not like I'm a witch and my DL# is my "true (system-given) name" and I disappear when they say it or something. Rather the parties who can hurt me are the ones who pretend knowledge of this semi-public information is an authentication system, and then hassle me with legal nastygrams when they get defrauded. Or who keep comprehensive dossiers on my behavior to unaccountably sort me into corporate-defined boxes so they can better extract my wealth and otherwise form anti-competitive arrangements against me. These actual attackers operate mostly according to the (very broken) law, and they are what needs fixing. Not just scaremongering when some bogeyman "wrong people" get a small taste of the exact same information.
Yes, it does. As far as water is concerned, air conditioners are open loop. Air conditioners make water from condensation forming on the inside (cool) coils. Modern window air conditioners then splash that water on the outside hot coils, to benefit from evaporative cooling. I haven't looked into the details about data center water usage, but I would guess the cited usage is from evaporative cooling.
reply