I suspect this would lead, not necessarily to improvement of the experiments themselves, but improvement of the descriptions thereof. I.e. rather than fixing the bug, document it so it's expected behavior.

Which is still an improvement!

Do commercial cloud providers already connect to Internet2? Should they? If they did, would it scratch this itch?

Is that what TFA already proposes, just in different words?

The test and measurement division known as Keysight was never closely related to any of the computer-hardware divisions.

And the server-hardware division known as HP Enterprise is actually Compaq, absorbed by merger. It doesn't even share much blood with the desktop PCs division.

...from the 32,768 power-on hours bug?

I'm not supposed to say which of these projects I worked on, but it was one of the most fun moments of my career, seeing it move for the first time.

After weeks of wiring, adapting plans that were evolving ever so slightly even as we built the truck, bringing up pieces so the software and integration team could do their part, crawling all over every inch of that monster frame, I knew what to expect. I knew it would be nearly silent, just a faint whine from the motor-axle. And I knew it would work, because we'd spun the wheels with the axles jacked in the air, to get all the encoders configured.

But it still took my breath away.

Because, you see, the whole rest of the prototype garage was still full of diesel trucks. They'd roar to life and rattle in and out, doing whatever their research programs were doing. I didn't have much insight into that, but I got accustomed to associating that racket with every moving truck. No matter what acoustic strides get made in passenger-car diesels, heavy-duty trucks never seem to get quieter. And after a few weeks in the garage, I was as used to it as anyone.

So when we finally lowered the jacks and moved the work tables out of the way, and it was time for the truck to move, part of my reflexes just knew that noise would accompany it. Even as I'd just spent hundreds of hours making sure the opposite was true, it nevertheless came as a shock. Seeing something that big just glide across the building with nary a hiss, I couldn't help but feel something serious had just changed.

I have asthma, and my doctor has advised me to take extra precautions. So when the email came out saying that remote work was even an option, I jumped on it and asked to begin immediately.

Difficulty is that my work is physical -- at the moment, building small wiring harnesses -- so it can't be done purely from a keyboard. So I'll pick up boxes of parts, and drop off completed units, off-hours (I know the building's alarm code) to minimize possible airborne exposure.

I'm still trying to figure out how best to sanitize the parts, if any. I've considered tossing the whole box in the oven preheated to 200F for a few minutes, since I believe that'll inactivate the virus and I know the parts and wires are all fine at that temperature.

I just closed the window and came back here to see if anyone had commented on it. Yup.

It's like a student just learned how to use the effects tool and decided that an absolute overdose thereof would somehow make it more watchable.

Sorry, BBC, whatever story you were trying to tell got lost in all the glitches.

Excellent article about why this is nothing new: https://berthub.eu/articles/po...

tl;dr: Through a combination of technical brain-drain and outsourcing, the providers have long since ceded control of their networks to vendors, contractors, and layers of sub-contractors. Huawei is just the tip of the iceberg, albeit a very real and threatening tip.

A flagship in 2013, the Galaxy S4 had half the RAM but otherwise nearly identical specs, a removable battery, a microSD slot, a headphone jack, and a glove-capable touchscreen.

And it can be had NIB/NOS for $65.

What's exciting about this again?

I'm not a podcast person myself, but on a recent roadtrip, my right-seat put on a few episodes of Darknet Diaries. Once I got over my initial annoyance with the over-the-top pseudo-badass tone in the intro and stuff, I was really impressed with the content.

I haven't listened to any more since, but I've recommended it to a bunch of people, including some who aren't quite as technical. Jack's way of explaining technical things with analogies, and sticking with that analogy throughout a given show, is really great.

If I had a longer commute, this would probably be on my list.

I can speak to the equipment question: Any receiver that can both receive Galileo and output raw data frames can theoretically be supported. In practice, the Ublox receivers are ubiquitous and cheap, everyone's using them, so they're the only ones supported right now. (Needs to be an 8-series or 9-series, I believe.)

I just bought an F9P and I'm hoping to use its multiple communication ports to act as both a Galmon receiver and an RTK base at the same time. We'll see! I just got shipping confirmations so I don't even have my hands on the hardware yet.

Holy crap, a 4-digit! ;) Hey Bert!

I was chuckling at the "new submitter" moniker, since I've been here since about 1997, just never got much into submitting stories, I guess.

I don't think the article is actually critical of the downtime, moreso the doublespeak about it. Claiming that the system is "better than GPS" but has an availability target of 77% is just weird. Claiming that one person caused it, when quite a lot of dominoes had been set up just waiting to be knocked over, is also disingenuous.

And FYI, I worked in telecom for ten years and had one service-affecting outage the whole time, which was contained to the maintenance window. I know a thing or two about redundant and reliable systems, and I think Galileo had all of those things. They were just ineffectively used, for reasons that boil down to bureaucratic bullshit.

They say that, but they also advertise that it's better than GPS.

That needs a big fat "*when it works at all".