I played SimCity in the past, along with Cities: Skylines. I enjoyed both, but it always felt weird, like I was handling things I wouldn't expect to handle.

100G on singlemode (100G-LR4 being the most common) uses the well-known two-strand ("duplex") fiber. Or you can get 100G bi-directional ("BiDi") over a single strand of singlemode (fiber-to-the-home often uses this).

100G on multimode is weird. As the name implies, one beam of light, sent down the core of a multimode fiber, results in multiple modes (search "Laser modes") being sent down the strand. As they overlap, it gets hard to get a clean signal out the other end.

To deal with this issue, 100G on multimode uses fiber cables containing multiple strands per direction of travel. MPO-8 and MPO-12 are common cables used for 100G multimode: It contains eight or twelve strands of fiber. Four strands are used to send, four to receive. And the prices for those cables are higher than standard duplex singlemode cable.

I checked in the Waymo app; it would be several blocks. Please reference the context "which I used to get to PT". I'm happy that, today, the extra blocks are doable. Some weeks ago, those extra blocks would not be doable.

Finally, besides the point of having to walk the distance, the main issue is the way in which the blockage is being conveyed to me: The Waymo app is not saying "We cannot get to you because of construction", the app is telling me that requests have been paused. Specifically, it's telling me "All of our cars are busy with riders right now" and "We're pausing requests in order to catch up — please check back again".

And although 20 minutes doesn’t seem much, the variability of airline baggage check and TSA means 20 minutes doesn’t seem an lead to increased stress.

There construction happening a block down the road from me. As part of the work, the rightmost lane is often blocked during the day (in between rush hours), so that things like concrete pumping can take place. The lane block starts just before where I live.

Around the same time, I noticed that when I would try to take Waymo (which I used to get to PT), I'd be told that things are busy and rides are paused. Recently, I've noticed that if I'm at work (or the PT place) and I want to take a Waymo back home, I'm told "Can't get to that spot right now".

If I had Waymo Premier, I wonder how hard it would be to get a refund on my subscription.

The above talks about a complete block (or, a complete-enough block) to using the service, but what about a major impediment? For example, let's say I travel regularly, and use Waymo to get to/from San Jose airport. Waymo's been disabling highway routes, which for me equates to 20-minute (or more) travel-time increase from home to airport. Would that be enough to qualify for a refund on the subscription?

No.

The reversion commit references https://github.com/RsyncProject/rsync/issues/959. In that GitHub issue is this comment:

> The change to zero memory was my idea and my change. It was a reaction to a security report I got which caused use of an element past the end of an array. By zeroing the allocation I could ensure that misuse of that memory if a similar bug came up in the future could only cause a null ptr deref, which is better than the chance of a valid pointer.

> It got a claude co-authored tag on it as I got it to do some tidy ups of a series of commits, and that is just what it does when it makes any modification. It doesn't mean the change was written by claude. It was written by me.

I think the person should report this to either the California DMV or CPUC, as well as the local airport authority.

For autonomous vehicles, I think people need to ‘normalize’ leaving one of the doors open until all people & cargo are out of the vehicle. The vehicle may complain, but it’s not going to drive off.

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

Points: 69

# Comments: 100

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 three open positions:

• 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://phxc1b.rfer.us/STANFORDbEHWH7

• Principal Storage Architect & Team Lead [HYBRID]: 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://phxc1b.rfer.us/STANFORD5.1WH8

• Storage Architect or Storage Sysadmin [HYBRID]: 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://phxc1b.rfer.us/STANFORDHPfWHA

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)!

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

Points: 47

# Comments: 39

The user originally wanted to do the transfer over WiFi. I helped them set up the transfer, and they eventually realized it would take multiple months to complete.

I set them up with a Thunderbolt 10GBASE-T Ethernet adapter. The wiring was Cat-6, but the distance was low enough such that 10G would’ve been achievable.

The switches in the network closet were only 1GbE, though the uplinks were 10GbE. Even so, switching the transfer from wireless to 1GbE wired brought our ETA down to just under one month.

I wish we could’ve gotten a 10GBASE-T port for the researcher; that would’ve brought the ETA down from ~1 month to ~1 week.

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

Points: 153

# Comments: 96

One of the benefits of a DID-like is that it can be parsed. Lots of folks have probably seen the DOI, a pointer to a specific publication. Here are two that folks might not know:

• The ORCID (https://info.orcid.org/researchers/), a unique ID for researchers, and a place for researchers to provide information about themselves, their affiliated institutions, and their publications.

• The RRID (https://rrid.site), a unique ID for research materials & tools. You can identify a specific antibody, or a specific DNA sequencer, or a particular HPC platform.

These are all centralized repositories of things (researchers, plasmids, instruments, …), all with the purpose of making it easier to identify, find, and connect things.