frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

LiteLLM Python package compromised by supply-chain attack

https://github.com/BerriAI/litellm/issues/24512
265•theanonymousone•2h ago•140 comments

Microsoft's "Fix" for Windows 11: Flowers After the Beating

https://www.sambent.com/microsofts-plan-to-fix-windows-11-is-gaslighting/
580•h0ek•5h ago•421 comments

So where are all the AI apps?

https://www.answer.ai/posts/2026-03-12-so-where-are-all-the-ai-apps.html
67•tanelpoder•36m ago•71 comments

Debunking Zswap and Zram Myths

https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-what.html
78•javierhonduco•4h ago•17 comments

curl > /dev/sda: How I made a Linux distro that runs wget | dd

https://astrid.tech/2026/03/24/0/curl-to-dev-sda/
85•astralbijection•4h ago•32 comments

Ripgrep is faster than grep, ag, git grep, ucg, pt, sift (2016)

https://burntsushi.net/ripgrep/
189•jxmorris12•8h ago•81 comments

Opera: Rewind The Web to 1996 (Opera at 30)

https://www.web-rewind.com
133•thushanfernando•7h ago•77 comments

Secure Domain Name System (DNS) Deployment 2026 Guide [pdf]

https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-81r3.pdf
26•XzetaU8•2h ago•0 comments

Nanobrew: The fastest macOS package manager compatible with brew

https://nanobrew.trilok.ai/
28•syrusakbary•3h ago•16 comments

Box of Secrets: Discreetly modding an apartment intercom to work with Apple Home

https://www.jackhogan.me/blog/box-of-secrets/
216•jackhogan11•1d ago•74 comments

Missile Defense Is NP-Complete

https://smu160.github.io/posts/missile-defense-is-np-complete/
126•O3marchnative•1h ago•102 comments

Log File Viewer for the Terminal

https://lnav.org/
239•wiradikusuma•9h ago•34 comments

NanoClaw Adopts OneCLI Agent Vault

https://nanoclaw.dev/blog/nanoclaw-agent-vault/
59•turntable_pride•2h ago•8 comments

I Quit Editing Photos

https://jamesbaker.uk/i-quit-editing-photos/
44•speckx•3d ago•40 comments

MSA: Memory Sparse Attention

https://github.com/EverMind-AI/MSA
53•chaosprint•3d ago•3 comments

iPhone 17 Pro Demonstrated Running a 400B LLM

https://twitter.com/anemll/status/2035901335984611412
672•anemll•1d ago•301 comments

Autoresearch on an old research idea

https://ykumar.me/blog/eclip-autoresearch/
395•ykumards•20h ago•86 comments

No-build, no-NPM, SSR-first JavaScript framework if you hate React, love HTML

https://qitejs.qount25.dev
88•usrbinenv•5d ago•74 comments

The Jellies That Evolved a Different Way to Keep Time

https://www.quantamagazine.org/the-jellies-that-evolved-a-different-way-to-keep-time-20260320/
4•jyunwai•3d ago•0 comments

LLM Neuroanatomy II: Modern LLM Hacking and Hints of a Universal Language?

https://dnhkng.github.io/posts/rys-ii/
22•realberkeaslan•4h ago•9 comments

BIO – The Bao I/O Co-Processor

https://www.crowdsupply.com/baochip/dabao/updates/bio-the-bao-i-o-co-processor
66•hasheddan•2d ago•17 comments

A 6502 disassembler with a TUI: A modern take on Regenerator

https://github.com/ricardoquesada/regenerator2000
70•wslh•3d ago•7 comments

FCC updates covered list to include foreign-made consumer routers

https://www.fcc.gov/document/fcc-updates-covered-list-include-foreign-made-consumer-routers
394•moonka•17h ago•260 comments

Show HN: Cq – Stack Overflow for AI coding agents

https://blog.mozilla.ai/cq-stack-overflow-for-agents/
182•peteski22•22h ago•77 comments

Dune3d: A parametric 3D CAD application

https://github.com/dune3d/dune3d
200•luu•2d ago•83 comments

Claude Code Cheat Sheet

https://cc.storyfox.cz
530•phasE89•17h ago•168 comments

Microservices and the First Law of Distributed Objects (2014)

https://martinfowler.com/articles/distributed-objects-microservices.html
37•pjmlp•3d ago•26 comments

Finding all regex matches has always been O(n²)

https://iev.ee/blog/the-quadratic-problem-nobody-fixed/
244•lalitmaganti•4d ago•63 comments

IRIX 3dfx Voodoo driver and glide2x IRIX port

https://sdz-mods.com/index.php/2026/03/23/irix-3dfx-voodoo-driver-glide2x-irix-port/
94•zdw•16h ago•24 comments

The Resolv hack: How one compromised key printed $23M

https://www.chainalysis.com/blog/lessons-from-the-resolv-hack/
103•timbowhite•16h ago•152 comments
Open in hackernews

A brief history of the numeric keypad

https://www.doc.cc/articles/a-brief-history-of-the-numeric-keypad
74•ThomPete•10mo ago

Comments

card_zero•10mo ago
> Picture the keypad of a telephone and calculator side by side. Can you see the subtle difference between the two without resorting to your smartphone? Don’t worry if you can’t recall the design.

Pfft, I have both on the table beside me. I live in a different timeline, I suppose.

tmtvl•10mo ago
What subtle difference? On a telephone the numbers are in a circle, whereas on a calculator they're in a square. They're completely different.
thenthenthen•10mo ago
I noticed ATM keypad in different countries use 1-2-3 or 7-8-9, I have yet to figure out if this is based on something, it seems fairly inconsistent with language/history/colonialism
throwup238•10mo ago
7-8-9 is the “standard” for calculator keypads but Bell Labs (supposedly) did some research and found 1-2-3 was more intuitive for users when designing the touch tone telephone keypads. When ATMs were being designed, manufacturers in the US/Canada/Europe emulated the telephone keypad while manufacturers in Asia emulated the calculator keypad.
signal11•10mo ago
These days you can get PIN-capable card-readers with touchscreens. Some of these models randomize the button layout, which can be interesting to those who rely on muscle memory to type their PIN. Especially given that some shops have the readers physically attached or secured, so you have to type the PIN at an odd angle.

Some examples here[1].

[1] https://ux.stackexchange.com/questions/144937/why-do-some-ne...

AStonesThrow•10mo ago
As I was briefly a beneficiary of SNAP EBT ("Food Stamps") I was subjected to the process of managing that debit card. When checking out, for example from Walmart.com, a popup would appear so that the user can input his PIN.

The popup was served by the SNAP EBT provider, and it would randomize the PIN number pad. So indeed, you couldn't rely on muscle memory to input your PIN because the number pad changed every time input was requested. It seemed that the mouse was also required for this input, rather than the keyboard.

userbinator•10mo ago
Relatedly, TV remote controls seem to have settled on the telephone layout with 1 in the top left.

I have also used a few kiosks with a keyboard that has its physical keys arranged in alphabetical order, which is just as confusing.

rmccue•10mo ago
Seems reasonable to have the most frequently used numbers close to the user; I wonder if there might be something of Benfold’s law involved, where lower digits are more frequently used. https://en.wikipedia.org/wiki/Benford%27s_law
EvanAnderson•10mo ago
That's my intuition. I spent a lot of time entering stacks of checks into 10-key calculators at my family's businesses growing up in the late 80s and mid-90s. Most entry used the bottom two rows of digits (the zero, double-zero, and 1-3)-- a lot of $10, $20, and $30 checks.
abanana•10mo ago
A line early on in the article caught my eye:

> they serve the same functional goal — input numbers

Well, yes and no. Same as how, when it comes to data types, it often has to be pointed out to inexperienced developers that a phone "number" isn't a number in the mathematical sense - you can't add or multiply 2 of them together to get anything meaningful. It's an identifying string, that happens to use only digit characters. "123" in a telephone number is three individual unrelated digits, whereas "123" in a calculator represents the number one hundred and twenty-three.

So the functional goal isn't exactly the same. One is entering individual characters, but on the other you're more likely to be thinking "one hundred and twenty-three" as you type its digits.

It may or may not be related to the actual reason for the inversion of layout, but the subtle difference felt like a (possibly minor) error in the initial premise.

ztetranz•10mo ago
It's sounds silly when the Android auto in my car reads a text message. "Message from twenty four thousand, five hundred and thirty nine ..."
Cordiali•10mo ago
Tangentially related, when websites mess up the digit grouping in phone number input fields, I've noticed it becomes quite hard to read. Must be a headache to get it right though, because it's a convention that changes from country to country, but it's easily worse than not grouping the digits.
toast0•10mo ago
Not that it's always right, but Google's libphonenumber has formatting rules for phone numbers that work pretty well. But you need to know the right country, which isn't always easy; people may enter a local number and the site context isn't always enough to know what country is implied.
tekla•10mo ago
> Picture the keypad of a telephone and calculator side by side. Can you see the subtle difference between the two without resorting to your smartphone?

I sometimes wonder if people have ever used Excel to calculate anything ever

wtallis•10mo ago
It's possible that at this point, a majority of the people who have ever used Excel to calculate anything have done so on a laptop that doesn't even have a numeric keypad. Certainly, that fraction of the cumulative historical Excel user base has been growing.
cduzz•10mo ago
I worked for a couple summers as a "relay operator"; in the USA there is (was? give the hateful time I suppose...) a law, "Americans with Disabilities Act" to the effect that people unable to do a thing should be able to do the thing. Roughly it means "people in wheelchairs should be able to access buildings" and "people unable to see should be able to read newspapers" and "people unable to hear should be able to talk on the telephone." and so on.

The "let people unable to hear talk on the phone" accommodation was to provide actual teletype machines to people who can't hear (at the time, many of these devices were some hideous 75 baud 6 bit monsters where there were limited punctuation and only upper case); the phone company would then also run a service where they had operators (I was one, for a couple summers) where people would call this service and that service would act as a bridge (or, "relay") to the other kind of device. So deaf people could order pizza, teenagers could call their friends and talk about teenager stuff, etc.

Specific to this conversation, the "relay operator" setup was a telephone system billing computer (that would also setup the phone call) and a standard terminal that'd interface with the person with the TTY. There were 2 800 numbers; one to connect to a TTY and one to connect to my ears; people would connect and ask to talk to a peer, and I'd enter the billing / call info into the phone computer, then actually do the talking on the terminal.

Each of these systems had a very distinct keyboard (the phone co keyboard had deep wells on the home keys; the terminal had "normal" nubs on the home keys), and I spent a ton of time entering phone numbers on the phone co's billing computer, with my right hand. To this day, my right hand touch-types "phone company" numbers and normal "ten key" (I did a lot of data entry at other points in my life) with my left hand.

[edit]

oh -- these things, though "ttys" were called "TDD" or "TTD" or some silly name to imply they were for deaf people, though they were just ttys; the cooler kids, calling that relay number, had 300 or 1200 or even 2400bps modems; I think that's as fast as the phoneco's relay terminal went, though)

GA

crazygringo•10mo ago
The article doesn't make it explicit, but from the facts it presents it seems like the fundamental difference between the numeric keypad and telephone keypad is:

- With the numeric keypad, you want an extra-large 0 at the bottom that can be operated with your thumb, because zeros are so disproportionately common in real-life numbers like prices. And smaller numbers are used more than larger numbers, so you put the smaller numbers closer to the 0 so you have to reach the least, and wind up with 7-8-9 at the top.

- With dialing phone numbers, zeros aren't more frequent -- in fact they're less because phone numbers can't start with them (in the US). For local numbers, all digits 1-9 are used with approximately equal frequency. So the keypad starts with a natural numeric order of 1-2-3 at the top in reading order, and puts 0 at the bottom since it feels weird to start counting with zero (just like QWERTY keyboards start with 1, and puts 0 after 9), and because it has the special function of calling the operator.

So there seems to be an actual logic to it.

gitroom•10mo ago
Man, reading all this makes my brain itch, I still mess up on ATM keypads if the layout flips. You think people just adapt even if it never makes sense, or does frustration actually change design over time?
teo_zero•10mo ago
Interesting research. Now I want an article about why in the top row of all computer keyboards 0 is right of 9 instead of left of 1.