frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

A worker fell into a nuclear reactor pool

https://www.nrc.gov/reading-rm/doc-collections/event-status/event/2025/20251022en?brid=vscAjql9kZ...
122•nvahalik•1h ago•79 comments

Pico-Banana-400k

https://github.com/apple/pico-banana-400k
28•dvrp•43m ago•2 comments

The Linux Boot Process: From Power Button to Kernel

https://www.0xkato.xyz/linux-boot/
95•0xkato•3h ago•33 comments

California invests in battery energy storage, leaving rolling blackouts behind

https://www.latimes.com/environment/story/2025-10-17/california-made-it-through-another-summer-wi...
191•JumpCrisscross•6h ago•153 comments

The Journey Before main()

https://amit.prasad.me/blog/before-main
154•amitprasad•7h ago•56 comments

I'm drowning in AI features I never asked for and I hate it

https://www.makeuseof.com/ai-features-being-rammed-down-our-throats/
130•gnabgib•2h ago•64 comments

Show HN: Diagram as code tool with draggable customizations

https://github.com/RohanAdwankar/oxdraw
121•RohanAdwankar•6h ago•23 comments

D2: Diagram Scripting Language

https://d2lang.com/tour/intro/
46•benzguo•4h ago•7 comments

How programs get run: ELF binaries (2015)

https://lwn.net/Articles/631631/
62•st_goliath•5h ago•1 comments

Agent Lightning: Train agents with RL (no code changes needed)

https://github.com/microsoft/agent-lightning
56•bakigul•6h ago•7 comments

An Update on TinyKVM

https://fwsgonzo.medium.com/an-update-on-tinykvm-7a38518e57e9
76•ingve•5h ago•16 comments

Doctor Who archive expert shares positive update on missing episode

https://www.radiotimes.com/tv/sci-fi/doctor-who-missing-episodes-update-teases-announcement-newsu...
49•gnabgib•6d ago•25 comments

Show HN: Shadcn/UI theme editor – Design and share Shadcn themes

https://shadcnthemer.com
83•miketromba•6h ago•22 comments

ARM Memory Tagging: how it improves C/C++ memory safety (2018) [pdf]

https://llvm.org/devmtg/2018-10/slides/Serebryany-Stepanov-Tsyrklevich-Memory-Tagging-Slides-LLVM...
47•fanf2•6h ago•16 comments

Rock Tumbler Instructions

https://rocktumbler.com/tips/rock-tumbler-instructions/
152•debo_•10h ago•75 comments

An Efficient Implementation of SELF (1989) [pdf]

https://courses.cs.washington.edu/courses/cse501/15sp/papers/chambers.pdf
36•todsacerdoti•5h ago•18 comments

AI, Wikipedia, and uncorrected machine translations of vulnerable languages

https://www.technologyreview.com/2025/09/25/1124005/ai-wikipedia-vulnerable-languages-doom-spiral/
63•kawera•6h ago•31 comments

We do not have sufficient links to the UK for Online Safety Act to be applicable

https://libera.chat/news/advised
202•todsacerdoti•9h ago•61 comments

WebDAV isn't dead yet

https://blog.feld.me/posts/2025/09/webdav-isnt-dead-yet/
104•toomuchtodo•1d ago•55 comments

In memory of the Christmas Island shrew

https://news.mongabay.com/2025/10/in-memory-of-the-christmas-island-shrew/
52•hexhowells•6h ago•16 comments

Belittled Magazine: Thirty years after the Sokal affair

https://thebaffler.com/salvos/belittled-magazine-robbins
35•Hooke•5h ago•24 comments

Ubios: China's Alternative to UEFI

https://pbxscience.com/ubios-chinas-alternative-to-uefi-and-the-new-era-of-firmware-standards/
12•1970-01-01•2d ago•5 comments

Passwords and Power Drills

https://google.github.io/building-secure-and-reliable-systems/raw/ch01.html#on_passwords_and_powe...
52•harporoeder•4d ago•15 comments

Testing out BLE beacons with BeaconDB

https://blog.matthewbrunelle.com/testing-out-ble-beacons-with-beacondb/
40•zdw•6h ago•12 comments

Show HN: LLM Rescuer – Fixing the billion dollar mistake in Ruby

https://github.com/barodeur/llm_rescuer
65•barodeur•1d ago•10 comments

Making a micro Linux distro (2023)

https://popovicu.com/posts/making-a-micro-linux-distro/
156•turrini•13h ago•27 comments

Project Amplify: Powered footwear for running and walking

https://about.nike.com/en/newsroom/releases/nike-project-amplify-official-images
49•justinmayer•6h ago•35 comments

Tarmageddon: RCE vulnerability highlights challenges of open source abandonware

https://edera.dev/stories/tarmageddon
65•vsgherzi•3d ago•30 comments

Honda's ASIMO (2021)

https://www.robotsgottalents.com/post/asimo
34•nothrowaways•6h ago•9 comments

The future of Python web services looks GIL-free

https://blog.baro.dev/p/the-future-of-python-web-services-looks-gil-free
180•gi0baro-dev•6d ago•75 comments
Open in hackernews

Passwords and Power Drills

https://google.github.io/building-secure-and-reliable-systems/raw/ch01.html#on_passwords_and_power_drills
52•harporoeder•4d ago

Comments

lanthade•5h ago
The power drill mention in the headline is a bit click-baity because in the end while a power drill was used it was unnecessary and was not the solution to the problem. Had they known how to properly use the hardware security devices they had the power drill wouldn't have been deployed at all.
Thorrez•5h ago
Well, it would have been necessary if they hadn't managed to find the employee in California who had the password for the California safe memorized.
hshdhdhehd•5h ago
There are lots of alternative ways this could have played out. Yes.
jumhyn•4h ago
But the additional cards may very well have been necessary to understand “there is something wrong with our usage of the cards, this error is not a one-off failure due to corrupted data or broken hardware or other problem local to the California card(s)”. Having multiple independent reproductions of an issue helps you narrow down what the commonalities are!
Daviey•3h ago
Sorry, but someone happening to have memory of the combination can also not be considered an adequate solution.
reader9274•3h ago
He clearly had the combination written down
Noumenon72•2h ago
The text says "Fortunately, another colleague in California had memorized the combination to the on-site safe". You might think that's unlikely and he probably wrote it down, but it's not "clear" from the text.
bfgeek•5h ago
> "At this point, the engineers in Australia decided that a brute-force approach to their safe problem was warranted and applied a power drill to the task. An hour later, the safe was open—but even the newly retrieved cards triggered the same error message."

What happened here (from what I recall) was far funnier than this does it credit.

The SREs first attempted to use a mallet (hammer) on the safe (which they had to first buy from the local hardware store - don't worry it got expensed later), then after multiple rounds of "persuasion" they eventually called in a professional (aka. a locksmith) who used a drill+crowbar to finally liberate the keycard.

The postmortem had fun step by step photos of the safe in various stages of disassembly.

netsharc•5h ago
What is this, sitcom slapstick? The slapstick of storing the security combination to the safe on the system that is locked by the card which inside the safe; and the slapstick of "You're inserting it wrong"...
kmoser•4h ago
> It took an additional hour for the team to realize that the green light on the smart card reader did not, in fact, indicate that the card had been inserted correctly.

I'm not sure which is worse: bad UI/UX use of lights, or inadequately trained engineers who misunderstood the lights.

GuB-42•2h ago
I'd go with bad UI/UX.

A lot of progress has been made by acknowledging that people are idiots and that the system has to work around that. Toyota, which went from one of the worst to one the most reliable automaker is known for formalizing idiot-proofing.

If the reader was able to read the card both way, there wouldn't have been a problem and no training required. The next best thing would be for the card to not fit upside down. Or have a clear message "try flipping the card". It is not something you should train people for, it should be obvious.

I also suspect the reader was in an unusual configuration, because everyone knows how to use smart cards and they probably did what they always do instinctively and it didn't work. On the thousands of times I did it, I don't remember having ever inserted my credit card the wrong way and don't remember anyone who did, it is just so instinctive. For an entire team to miss that, there must be something wrong with how the reader is set up.

chasing0entropy•46m ago
Agree.

The fundamental lesson of at least half my information systems undergraduate courses was you adapt the system to observed user behavior, do not expect the user to adapt their behavior to the system.

mtlynch•3h ago
Sorry for the offtopic comment, but it's bizarre to me that Google is hosting their book on Github with a github.io domain. Their previous two SRE books are hosted at https://sre.google on Google-owned IPs.[0]

What was that decision process? "We're Google, and we're literally writing a book about how good we are at hosting services. But hosting some static HTML files that are almost entirely text? That's a tough one. We'd better outsource that to one of our competitors."

[0] https://sre.google/books/

nashashmi•2h ago
I think one is a portal for GitHub developers, while the other is a public polished site. I reminisced the early Google forthright attitude that made life so simple and human.
kingforaday•1h ago
What I really like about this story is that Google for all that they are still have normal fallible people just like us behind the scenes.