Mine was 10 trillion today. At first I thought it was a lot, but then I realized its still smaller than the US national debt, so it cant be that bad.

I wonder how many systems actually care? I presume the core NTP servers handle this well, and most systems just feed off of that?

GPS satellites probably handle it well too, but maybe some consumer or even industrial GPS receivers don't? Maybe some trading systems? I don't think crypto systems care too much.

I wonder if there's things that run 24/7 and need to be monitored.. e.g. if you have oil flowing through some pipeline at 100 liters/second, one particular minute will have 6100 liters, and someone will want to get paid for that 100 extra liters.

But the meter/reporting tool would say "Well, we measure every second, and the meter reported a constant rate of 100 liter/second, and as we know we have 60 seconds in a minute, so we got 6000 liters!".

Or a database for "measurements every second for this minute" that has 60 fields, and don't have a field for the 61st measurement.

I once worked with smart meters for electricity consumption that do run 24/7. Leap seconds were not an issue but we had a very similar one now that I think about it: DST shenanigans!

Like how much time is there between 2 and 3 am? Usually one hour, but sometimes 2 and also sometimes 0. It looks simple at first but it creates a lot of edge cases that your business logic now needs to handle and we had a fairly complex system for this.

I can relate:

My son is born at 02h30 right DST change time.

It tooks 3 f*cking days to get his birth registered in the Hospital new birth registration system.

The hospital (at the time) just got digitalized and most systems where not able to agree if he was born after or before DST changes.

PS: I guess he is born fated to be a software QA later on.

This commenter says he has different birth dates in different countries' sytems, which is correct if you consider the exact time of birth, but... that's probably a bug? https://news.ycombinator.com/item?id=48853128

No matter what the 100 liters of mystery fluid are worth, if the pump is running continually, the billing for that day would only be off by .0011574%, so either side can probably afford to absorb the loss.

Though if it's valuable enough it could of course be "worth" paying top dollar to have engineers solve a ludicrous non-issue.

Now imagine blood pump during surgery.

I’m horrified to imagine a blood pump or any life support system being network connected, or to rely on the precise time of day in order to function correctly. Accurate time keeping for anything in this realm can and should be done without a network.

The equation is different if the life saving surgery couldn’t be performed otherwise. Still pretty crazy and I don’t know how comfortable I’d be with it if I were the patient.

Systems definitely care, especially in finance and trading systems.

Was involved in rolling out a large NTP annealing patch about ten years ago. We missed a couple and the effect was largely overall muted, but we did have one server with an old JVM hard crashing the server right at the second shift.

That specific server was already hobbling along so it wasn't a surprise. But it required a bit of firefighting.

GPS uses its own time base that doesn't do leap seconds. For display purposes, the leap second offset to UTC is transmitted to the receivers and added to the displayed time if needed.

The problem frequently crops up in order-deterministic systems that use time and haven't accounted for the edge case of all the vagaries related to time-keeping of this being only one.

I've worked on some extremely sensitive systems that had thousands of lines of C dedicated to handling skewing a time gap across an hour-per-second when necessary. I know that code assumed only "missing" time (jump-forwards)... Even knowing what I know as a developer now, if I was re-implementing that system from scratch and didn't have this top-of-mind, I'd bet I would miss "overlapping" or "duplicate" time entirely.

Maybe that is more of a me problem than others, but I'd bet there are some safety critical systems out there where the responsible engineers, QA, and specs all missed this as well.

traditional markets are closed when time changes happen

There are true ZKP setups where no one learns anything but the absolute minimum (e.g. is this person over 16, not what is their dob). This is hard to prove though and I don't know if I trust Google to do it

It sounds like none of the data will be reliable? Ai and community seems like very little will be true and I will have no idea which part will be true.

Crunchbase is also not very reliable. It's community/self-reported data.

Crunchbase is generally self reported data

I'm pretty nuclear, but I don't understand how having nuclear power prevents vulnerability to direct attack? If anything it would concentrate your risks - your energy now comes from fewer, more centralized and more fragile sources

> I'm pretty nuclear

I'm atomic, FWIW.

> how having nuclear power prevents vulnerability to direct attack?

OP alluded to a well-known bonus capability of nuclear power plants: https://en.wikipedia.org/wiki/Plutonium-239#Production

it's very hard to create plutonium for weapons this way due to parasitic isotopes. Much easier to have distributed enrichment or uranium.

risks are concentrated with ren too. Where do you think most EU offshore is built? Where are most productive solar units? What you do with gas firming plants. You always have centralization problem at different levels. Prime example - most of Ukraine's ren capacity is either destroyed or conquered because it was in south where weather is better

Isn't this the whole point of an AGENTS.md file? So that you can leave the readme for humans and put LLM-friendly crap in a separate file?

The Fifa hack had nothing to do with JWTs, it was because FIFA was doing auth on the client side. They would have had the same issue if they used cookie auth.

h4ckernews also accessed an Azure Function App that provided direct download URLs for internal FIFA files, including transfer reports and board level data, due to a lack of RBAC access checks.

what the hell do you mean they were doing auth client side? how is this possible with infinite budget?

"You're holding it wrong" would beg to differ, not to mention the many flops he had (remember the magic mouse?).

He was smart & very successful. I wouldn't call him relatable to most humans.

Honestly my biggest pain point with all personal accounting systems was that there was no easy, free way to automatically pull my transaction data from all my accounts into a single, local file that I can play with as I want. I really don't want to go to all my accounts every month and click download.

There still isn't, but I did recently find simplefin(https://beta-bridge.simplefin.org/). Its not great (e.g. quota of only ~25 requests per day), but its good enough and the price was cheap enough that I just bit the bullet. It also paired well with Actual budget, and now I have a personal accounting system that I am reasonably happy with.

I also found teller.io, which is frankly a better dev experience (and good free tier!), but they don't support all the banks I'm on and somehow simplefin does.

It would be nice if financial institutions simply created end-user/app centric APIs for consumption... As it is, the best you can do is something akin to puppeteer with a real browser agent and your authentication credentials and scraping... I mean there can be APIs underneath, but there's not a good open resource/repository that I'm aware of...

Would be nice/interesting to see something like that come about, but It's a bit frustrating. A delegated read-only api key against a specific account shouldn't be that hard to do.

I've slowly built up a set of scripts to do this: too many different methods, but eventually I get csv files for each account, then hledger import - and finally I manually fix up details

I have a friend that worked in NYC in part of the DOE (not a teacher, but something adjacent). Its a union position, so during COVID when everyone was getting remote, her profession got remote too.

53 minutes per week.

53 minutes. Not even a full hour. It was specific enough that you knew some bureaucrat went out of their way to hyper optimize this, creating a maximum slap-in-your-face effect.

This 30 minutes thing feels the same way.