A long time ago, I'd participate in things like CAcert in-person assurance, PGP key-signing, etc.. I think a model like that would've been useful here: An AgeKey issued/signed by two people. I think of it like a decentralized equivalent to someone's parents saying "Yeah, $CHILD is old enough", or to a cashier saying "This person obviously looks old".
The best way to ask for this is to send an email, to the email address which you can find at the bottom of the page (click on "Contact"). There's no guarantee that the mods will find your comment otherwise.
Over on Youtube the Usagi Electric channel has several videos about reviving old vacuum tube computers and one of the interesting aspects is that tube failures are much less of an issue than the germanium diodes. The tubes are large and dramatic, but they're heavily outnumbered by the diodes. It was such a problem that the company built specialized test equipment that could identify bad diodes on the cards.
Vacuum tubes don't have the longest "natural" lifespan, but you also have to remember that early manufacturing techniques mean a lot more "bad batch" variability.
When part performance is more unpredictable, ease of maintenance is a much bigger deal for everybody all across the price/quality range.
> I'm also curious, if the cathode was grounded to the machine frame, how dangerous was it to do work on those machines?
When ground means earth, then: The chassis isn't dangerous at all. Its potential relative to other nearby things that are also connected to earth is ~0v.
When that's used as a supply rail (like for the cathode), it still works fine. It's still tied to earth.
You don't want to put any of your dinguses betwixt that and the +150v plate rail, but... I mean. :)
Stanford Research Computing | Stanford, CA (next to Palo Alto) | Full-time | Four positions | HYBRID,ONSITE
Stanford Research Computing (https://srcc.stanford.edu) is a collaboration between University IT and the Vice Provost and Dean of Research. We operate HPC environments for researchers, we do one-time consultations on projects (from software and pipelines, to data management, to physical building design and fit-out), and we provide contract support for individual Labs, Departments, and Schools.
We have four open positions, three hybrid and one (marked) onsite:
• Principal Storage Architect & Team Lead: Our current storage team lead is moving on to Industry, so we're splitting his work into two separate roles. This is the Technical Manager position: You'll be leading the storage team, setting the direction for our large storage environments: Oak (file storage, used by multiple cluster), Fir (fast scratch for Sherlock), and Elm (object storage on top of tape). Knowledge of Lustre, Infiniband, and PB-scale storage is important. More info: https://bit.ly/44PbQnr
• Storage Architect or Storage Sysadmin: This is the second role I referenced above. You'll be maintaining & expanding Oak, our 20+ Pebibyte Lustre storage environment used by our largest HPC clusters. Depending on your experience level, you might also have some responsibility for Elm, which provides object storage on top of tape. Knowledge of Lustre, Infiniband, and PB-scale storage is important here, too. More info: https://bit.ly/4y8lj6R
• GPU System Engineer: We are looking to hire a lead sysadmin for Marlowe—our 1SU NVIDIA DGX H100 SuperPOD with DDN Intelliflash and DDN NFS storage—launched. You'll be working with the latest AI/ML/Deep Learning/LLM software & frameworks, getting them to work in an HPC environment. You'll be keeping the environment up-to-date, and working with NVIDIA/DDN when there's trouble. You should also expect to interact with users & PIs a lot. More info: https://bit.ly/4vf7aly
• HPC Hardware & Infra Sysadmin [ONSITE]: We are looking for a system administrator to help run the hardware & infrastructure portions of Sherlock, our largest HPC cluster. Sherlock is a mix of Intel & AMD x86_64 servers, with three Infiniband fabrics, plus an Ethernet backbone. You'll be responsible for maintaining, troubleshooting, and improving the hardware of Sherlock. That is, keeping things working, and figuring out how to make it better. More info: https://bit.ly/3SPRpnJ
If you don't already live in the Bay Area, we provide a relocation incentive. Depending on where you live, we provide free transit passes. Unfortunately, if you drive, you will have to pay for parking for the days you're on-site. There is some on-call around the holidays. We get a 403(b) match, good healthcare, and 30+ days off per year (holidays + vacation). All Benefits are all publicly documented at https://cardinalatwork.stanford.edu/benefits-rewards.
If you have questions, feel free to reply here or email me (the info is in my profile)!
Stanford Research Computing | Stanford, CA (next to Palo Alto) | Full-time | Three positions | HYBRID,ONSITE
Stanford Research Computing (https://srcc.stanford.edu) is a collaboration between University IT and the Vice Provost and Dean of Research. We operate HPC environments for researchers, we do one-time consultations on projects (from software and pipelines, to data management, to physical building design and fit-out), and we provide contract support for individual Labs, Departments, and Schools.
We have four open positions, three hybrid and one (marked) onsite:
• Principal Storage Architect & Team Lead: Our current storage team lead is moving on to Industry, so we're splitting his work into two separate roles. This is the Technical Manager position: You'll be leading the storage team, setting the direction for our large storage environments: Oak (file storage, used by multiple cluster), Fir (fast scratch for Sherlock), and Elm (object storage on top of tape). Knowledge of Lustre, Infiniband, and PB-scale storage is important. More info: https://bit.ly/44PbQnr
• Storage Architect or Storage Sysadmin: This is the second role I referenced above. You'll be maintaining & expanding Oak, our 20+ Pebibyte Lustre storage environment used by our largest HPC clusters. Depending on your experience level, you might also have some responsibility for Elm, which provides object storage on top of tape. Knowledge of Lustre, Infiniband, and PB-scale
storage is important here, too. More info: https://bit.ly/4y8lj6R
• GPU Cluster Sysadmin: With Marlowe—our 1SU NVIDIA DGX H100 SuperPOD with DDN Intelliflash and DDN NFS storage—launched, we have decided to hire an additional sysadmin! You'll be working with the latest AI/ML/Deep Learning/LLM software & frameworks, getting them to work in an HPC environment. You'll be keeping the environment up-to-date, and working with NVIDIA/DDN when there's trouble. You should also expect to interact with users & PIs a lot. More info: https://bit.ly/4vf7aly
• HPC Hardware & Infra Sysadmin [ONSITE]: We are looking for a system administrator to help run the hardware & infrastructure portions of Sherlock, our largest HPC cluster. Sherlock is a mix of Intel & AMD x86_64 servers, with three Infiniband fabrics, plus an Ethernet backbone. You'll be responsible for maintaining, troubleshooting, and improving the hardware of Sherlock. That is, keeping things working, and figuring out how to make it better. More info: https://bit.ly/3SPRpnJ
If you don't already live in the Bay Area, we provide a relocation incentive. Depending on where you live, we provide free transit passes. Unfortunately, if you drive, you will have to pay for parking for the days you're on-site. There is some on-call around the holidays. We get a 403(b) match, good healthcare, and 30+ days off per year (holidays + vacation). All Benefits are all publicly documented at https://cardinalatwork.stanford.edu/benefits-rewards.
If you have questions, feel free to reply here or email me (the info is in my profile)!
Coal was made unprofitable by fiat and the plants were demolished (supply decreased).
Then, datacenters (demand increased, to put it mildly).
The explanation that one chooses for this is a function of one's other politics but the fact is, one has become a political rallying cry (opposition to demand increase) and the other (blame for supply decrease) has not, and this is the discussion we find ourselves in.
- never actually shows how these new data centers are driving up electricity costs
Funny. They imply causation but never show it. If they had evidence that data centers caused this 25% increase, or a large percentage of it, dont you think they would show it?
Actually, you could write the exact same article but sub out data centers with the clean energy rollout.
This is a popular social media take that is being pushed very hard by clickbait and doomposters, so it's not exactly going against the tide.
Social media is always trying to make things sound way worse than they are and journalists are always in a rush to latch onto those trending keywords, and artificially spin headlines vaguely connected to the topic. So if you only skim headlines it's easy to think something is a bigger problem than it is.
There are other lines in the post that, to me, provide clarity.
First is this, the second paragraph:
> British-based employees at the Wikimedia Foundation (WMF) wrote a letter to management today (Wednesday 24thJune) requesting their right to be represented by the United Tech and Allied Workers (UTAW) section of the Communication Workers Union (CWU).
That makes it clear that this is regarding the "British-based employees at the Wikimedia Foundation". Yes, the headline does say "Wikipedia": I expect the CWU chose that because many more folks know what Wikipedia is, vs. the Wikimedia foundation.
Second is this:
> Over 1000 Wikimedia volunteers and community members have also signed petitions in support of the workers, who have networked globally under the banner of Wiki Workers United (WWU).
I view terms like "[wikipedia] editors" as terms of art: "Editor" in the Wikipedia context maps to the more-generic "volunteer" in the broader context, which is why the post is referring here to "volunteers and community members".
So, I don't see any inconsistency in the article, but I see how the current post title can make it confusing.
In my opinion, I think it would be appropriate for you to email the HN folks, to ask the title be changed to something like "Wikimedia Foundation Workers to Seek Union Recognition".
reply