Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Jemalloc 5.4.0(github.com/jemalloc ↗)
    39comments
  2. The scourge of x86 emulation(fex-emu.com ↗)
    24comments
  3. OpenJev(openjev.com ↗)
    1comments
  4. Astra for Law(openai.com ↗)
    546comments
  5. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    131comments
  6. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    219comments
  7. Qwen 3.8 Omni Flash(qwen.ai ↗)
    80comments
  8. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    169comments
  9. When the fractional part of a float fixes your shader(crocidb.com ↗)
    1comments
  10. Pre-Greek: The lost language hidden within Ancient Greek(linguisticdiscovery.com ↗)
    34comments
  11. Wax motor(wikipedia.org ↗)
    70comments
  12. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    231comments
  13. A heap overflow and SSO misconfiguration to compromise OpenAI internal repos(hacktron.ai ↗)
    153comments
  14. Shapelearn Qwen 3.8 27B (13.1 GB VRAM)(byteshape.com ↗)
    11comments
  15. Replacing Pull Requests with Delta(zed.dev ↗)
    2comments
  16. How to Write with an LLM(sockpuppet.org ↗)
    96comments
  17. Speeding up gearhash on ARM64(sam.dev ↗)
    discuss
  18. Ask A Monk – A digital wilderness for thoughts with no immediate answer(askamonk.online ↗)
    23comments
  19. Why Does the Universe Expand?(cosmicave.org ↗)
    53comments
  20. Flet 1.0 – Build cross-platform apps in Python(flet.dev ↗)
    56comments
  21. Telstra outage: The night a network decided the year was 2006(netnod.se ↗)
    24comments
  22. Diplodocus, Long Thought Exclusively American, Turns Up in Spain(sci.news ↗)
    41comments
  23. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    368comments
  24. How do we prevent mathemathics from devolving into the Medieval Era of secrecy?(mathoverflow.net ↗)
    106comments
  25. Microsoft exec called AI scraping 'the largest theft of labor in human history'(techcrunch.com ↗)
    1comments
  26. CrowdSec Source Code Leak(crowdsec.net ↗)
    48comments
  27. The most important product decision is what you don't build(liamnugent.me ↗)
    38comments
  28. Apple detectives solved mystery of ancient tree and rewrote the history of fruit(scientificamerican.com ↗)
    10comments
  29. Fixing an NZXT Signal 4K30 part 2: the green/pink video bug(downtowndougbrown.com ↗)
    10comments
  30. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data(arxiv.org ↗)
    39comments

Telstra outage: The night a network decided the year was 2006

56 pointsby 8h agonetnod.se
24 comments
8h agoHN ↗

Shout out to the Jeff Geerling video about this

8h agoHN ↗

Author needs to decide which end of the stratum stack they want as the top.

This design from 2010 had at the top stratum 1 sources at Australia's National Measurement Institute (NMI)

Among otherwise comparable candidates, the lower stratum carries more weight.

7h agoHN ↗

Each decision solved the problem in front of it. Nobody was asked to look at the sum of all actions.

This is the perfect description of Telstra as a company.

5h agoHN ↗

This reminds me of this: https://obamawhitehouse.archives.gov/blog/2015/03/26/why-we-...

I saw the talk version of that and it has lodged in my memory. The point he made was that "health.gov" was made by a bunch of teams that made sure that their part worked, but nobody was in charge of making the whole thing work.

This is sadly "normal" for large bureaucracies.

Every time I see a giant, multi-million dollar catastrophe, it's always "proper", "documented", "enterprise", "by the book", and... "a total failure". The reason is always that nobody actually cares about the final outcome, only the paperwork in front of them that they need fill out, the checkbox that needs to be ticked, or the compliance requirement that needs to be met.

3h agoHN ↗

This, in my opinion, is some part of how we are schooling people - do as you are told and follow the rules and some part of not having stakes in the outcome.

3m agoHN ↗

No this is what the corporate world does to you.

There's a brief period when you join any company where you really want to improve things, and then about a year in the system has asserted towards the mean.

Nothing to do with schooling, every thing to do with business structures.

2h agoHN ↗

Why did you include the source tracker in your link?

2h agoHN ↗

Definitely not on purpose! I keep forgetting that ChatGPT does that now, which is rather irritating because I don’t use it to write comments but the tracker makes it look like I do.

I do use ChatGPT to resolve vague memories of articles read long ago into concrete URLs I can share, which is one of the best uses of the accursed things right now!

I assure you that I am an organic meat human like yourself and the article dates itself to the “before times” and can also be trusted to be free of contamination.

2h agoHN ↗

ChatGPT is a far more useful search engine than Google, duckduckgo, etc.

It won’t last, but just as Google was so much better than hotbit, altavista, yahoo etc back in the day.

5h agoHN ↗

They're pretty readable, I recommend that second one (though it leaves some questions I have unanswered). It's a good example of how latent issues with a large system can go unrecognised for a long time before a seeming unrelated change can trigger a cascading failure

4h agoHN ↗

One thing it doesn't make clear – the GPS card only supported the original L1 signal, which is what causes the GPS week rollover issue. The newer L2C signal has a much longer rollover period (157 years vs 19.6 years), which means no rollover until next century. If the GPS card had supported the newer L2C signal, then likely this would not have happened even if the other misconfigurations had still occurred.

6h agoHN ↗

All I could think of while reading this was “has no one heard of ntptrace?”

6h agoHN ↗

It's funny, but I had the same thing happen to me once. One day, overnight, my computer decided it was 2006.

It happened twenty years ago...

;-)

4h agoHN ↗

Is it really so that Time Division Multiplex timing in cellular networks is based on NTP time? I stopped reading after the article implied this - it doesn't sound plausible at all.

4h agoHN ↗

No, it absolutely is not.

That timing requires a very tight time, frequency and phase reference. It’s derived from local high stability GNSS-disciplined time references.

1h agoHN ↗

I would assume it’s similar to dab etc, and it’s ptp that carried that data on IP. In the broadcast tv world we use ptp, or more traditionally black and burst, or word clocks in audio.

The source is still the same - your grandmaster (ptp) or sync generator (b+b) is fed from a good timing source - often GPS, with one or two inputs, but sometimes local atomic clocks.

I’ve seen issues before with 40ms audio gaps when a GPS antenna has died and the coders can’t cope with frame drift so they incentive a 40ms silence in the audio every 40 minutes or so as the source and destination clocks are different speeds by about 1 part in 60,000.

In DAB the tolerances are far lower, there was a problem about 10 years ago due to a GPs satellite being a few microseconds off

https://www.radioworld.com/trends-1/gps-anomalies-caused-pro...

1h agoHN ↗

No. The official report seems to suggest that software in IMS core (the subsystem that controls VOIP signalling in the mobile network) bugged out after the time was shifted back 20 years. That doesn't narrow down the specific failure that stopped calls from going through very much. IMS core is full of timers, but it could also have been a license server issue for all the report said about it.

3h agoHN ↗

Human made summary: A telecom company had time synchronisation issues in a location of their infrastructure. They eventually used a single hardware GPS clock that fixed the issues but became their only authoritative clock in this location.

One day, the clock was turn off and on and it went 1024 weeks backwards because the time GPS time protocol sucks and use a week counter with too few bits.

Apparently a GPS clock can keep track of the time if it’s up and running when the week counter overflows, otherwise it has to take a wild guess. Apparently their hardware GPS clock used a hardcoded start time from its firmware instead of trusting a less reliable existing clock.

The article finishes with some AI looking suggestions to prevent such an issue to happen again.

Mine would be to have bought one or two more GPS clocks and not from the same provider.