frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Git for US Legislation

https://lexifina.com/blog/git-for-the-us-code
44•alansaber•1h ago•25 comments

Genie 4

https://deepmind.google/blog/genie-4-a-new-generation-of-world-simulation/
774•acossta•11h ago•469 comments

Ink droplets in motion snag top prize in Nikon Small World contest

https://arstechnica.com/science/2026/10/meet-the-2026-winner-of-nikons-small-world-photomicrograp...
100•_Microft•2d ago•15 comments

Ghostty 1.4

https://ghostty.org/docs/install/release-notes/1-4-0
820•deaux•10h ago•246 comments

Early progress on accelerating drug development with Claude

https://www.anthropic.com/research/early-progress-drug-development
154•dataking•6h ago•142 comments

Tailscale SSH: Investigation and remediation update

https://tailscale.com/ssh-investigation-update
218•figmert•7h ago•114 comments

Survival LLM: AI assistant and emergency library that runs on your own computer

https://www.brangus.io/survival-llm
216•Luc•7h ago•112 comments

Tabletop Whale is an original science illustration blog

https://tabletopwhale.com
20•Levitating•4d ago•3 comments

Assembly Nights

https://ratfactor.com/assembly-nights
11•andsoitis•2d ago•0 comments

Raspberry Pi Zero 3W and Pi 4 Model A spotted in device trees

https://bret.dk/raspberry-pi-zero-3-w-pi-4-model-a/
113•sthlmb•6h ago•46 comments

81 Jokes for the ZX81

https://spelk.press/gb/products/81-jokes-for-the-zx81
47•robin_reala•1d ago•3 comments

New 14‑inch MacBook Pro with M6

https://www.apple.com/in/newsroom/2026/10/apple-introduces-the-new-14-inch-macbook-pro-with-m6/
298•beex•11h ago•382 comments

Python's experimental JIT to be removed

https://lwn.net/SubscriberLink/1102102/0c00e4d550f25f8c/
459•f311a•16h ago•247 comments

An examination of lost firefly species of the US and Canada

https://journaloflostspecies.org/index.php/jls/article/view/37/33
98•bryanrasmussen•3d ago•18 comments

New iMac with M6

https://www.apple.com/imac/
317•notfried•14h ago•387 comments

Classification of Finite Simple Groups Formalized in Lean

https://cfsg.axiommath.ai/
178•pfdietz•10h ago•45 comments

Reviewers rarely talk about reliability. Owners bring it up twice as often

https://www.bettascore.ai/research/reliability-reviewers-vs-owners
72•tsxng•4h ago•70 comments

Four Months of Zig

https://gracefulliberty.com/articles/four-months-of-zig/
83•ibobev•7h ago•50 comments

Radio-tagged Monarch butterflies

https://news.vt.edu/articles/2026/10/cmi-monarchs.html
37•rdmuser•9h ago•11 comments

'Forced out': HOA fees to rise to $2,500 a month

https://www.wsoctv.com/news/local/forced-out-hoa-fees-rise-7500-month/XCW2HIHUKNBMTNWVQSYXQZJCY4/
11•hippich•2h ago•5 comments

SS United States to be sunk as largest artificial reef

https://divemagazine.com/scuba-diving-news/ss-united-states-to-be-sunk-as-worlds-largest-artifici...
101•geox•1d ago•72 comments

US Government is hiding a secret court ruling about how it spies on Americans

https://www.wired.com/story/the-us-government-is-hiding-a-secret-court-ruling-about-how-it-spies-...
827•helterskelter2•13h ago•297 comments

Hex Raises $100M

https://hex.tech/blog/hex-new-era/
60•tomwphillips•6h ago•36 comments

Moxnox 1.0: NT-Like, POSIX-Compatible OS Running Atop Btrfs

https://github.com/maharmstone/moxnox
23•SockThief•3h ago•3 comments

Nvidia and Micron Make Up 34% of America's Earnings Boom

https://www.wsj.com/finance/stocks/the-earnings-boom-is-heavily-reliant-on-just-a-handful-of-stoc...
101•JumpCrisscross•2d ago•15 comments

Introducing LFM3: Every Modality for Specialized Intelligence

https://www.liquid.ai/blog/lfm3
127•Philpax•10h ago•51 comments

Expanding our partnership with GSA to bring Claude to all levels of government

https://www.anthropic.com/news/expanding-partnership-gsa
29•matthieu_bl•4h ago•16 comments

Why Micron Is Suddenly Ditching 4F² DRAM as Rivals Double Down

https://hothardware.com/news/why-micron-is-suddenly-ditching-4f-dram
146•rbanffy•1d ago•22 comments

Code-execution flaw in UEFI firmware threatens most servers on planet Earth

https://arstechnica.com/security/2026/10/code-execution-flaw-in-uefi-firmware-threatens-most-serv...
42•DamnInteresting•6h ago•8 comments

Land Value Capture in Practice: Ethiopia's Urban Land Lease System

https://blog.landeconomics.org/p/land-value-capture-in-practice-reflections
49•surprisetalk•1d ago•9 comments
Open in hackernews

Git for US Legislation

https://lexifina.com/blog/git-for-the-us-code
42•alansaber•1h ago

Comments

octoberfranklin•54m ago
Fraudulent title, you can't git-clone this.
doezi•36m ago
Not really. It is arguing for version controlled legislation. So who’s responsible for what portions of literal laws and policy. I hope your "not clone-able" is in jest
JumpCrisscross•32m ago
> who’s responsible for what portions of literal laws and policy

This makes sense for bills. It doesn't for laws. Once a bill is a law, it's the will of the Congress.

rileymat2•28m ago
You could tag yes/no/abstains to it.
dathanb82•17m ago
That’s like saying that the code in a repo belongs to the whole team once a PR is merged, so it doesn’t make sense to track its provenance back to its original authors.
JumpCrisscross•10m ago
> so it doesn’t make sense to track its provenance back to its original authors

The legislative process is inherently collaborative in a way that's ordinarily undocumented. Who introduced an amendment and who supported it are entirely separate. Someone who introduced language can wind up not supporting it because of where the mix of trade-offs winds up.

At the level of a bill, knowing who wrote language matters. At the level of law, you should only care who voted for it.

mushufasa•50m ago
I'm not an expert in this domain but I'm aware there has been prior work to attempt this. I'd appreciate if someone knowledgeable could post some of that context.
7kago_yomi•36m ago
Unlike code, natural language laws have many exceptions and context dependencies, so trying to manage them cleanly with Git seems like it would be tough as data structuring costs and exception handling (hardcode-style responses) increase.
JumpCrisscross•33m ago
> natural language laws have many exceptions and context dependencies

The complexity is in common law, not natural-language laws.

The U.S. Code and Code of Federal Regulations can be completely presented through a Git-like system. The complexity comes in when attaching court cases.

7kago_yomi•24m ago
I see. The laws are completely different from my country, so this is very educational. My country uses civil law, but I see that is how it is under common law. Thank you very much.
TomAbel•28m ago
Reminds me of a similar project for french law

French bills evolution versioned in git and visualized The Law Factory: french bills as git, opendata and dataviz https://www.lafabriquedelaloi.fr/

"Law is Code" on The Law Factory: french bills as git, opendata and dataviz - https://news.ycombinator.com/item?id=7817357 May 2014 (0 comments)

xlayn•21m ago
YES PLEASE, but I suspect it will degenerate into another paid service with 1000 tiers... I think you cannot access the US law without paying for it? odd... I will wait for claude law to appear and hope they share the torrent...
Matticus_Rex•13m ago
Legislation you can generally access for free. Case law you often cannot.
iAMkenough•10m ago
Should that change? In my opinion, in the age of AI, both should be generally accessible for free.
macintux•5m ago
Electrical & building codes are also paywalled, IIRC.
burnJS•21m ago
I had this idea over 10 years ago but never finished it. I hope this takes off. I do fear it's not very practical for many big pieces of legislation which are often written in secret.
Ericson2314•13m ago
Don't worry about that. Even if we only saw voted-upon revisions in the Git history, it will still be a huge improvement.

Version control for the public parts will make both public and secretive law-drafting better.

EddieRingle•4m ago
Likewise, a younger, more idealistic me thought it'd be great to use a GitHub-esque platform for laws. Pull Requests to suggest laws, gated behind reviews/approvals, branches so each house could work on their own versions before finally reconciling and merging into the Code, literally.
iAMkenough•20m ago
Sounds neat, but not something a private company should be responsible for.

If transparency is the goal, the entire codebase for this should be public domain and not profitable. Otherwise there's a profit motive to rewrite history.

counters•12m ago
Major party foul for not calling this "legitslate"
barrrrald•11m ago
Cool idea but I can't find anywhere on the linked page to try it? It reads like a neat concept but it's not clear if this is a thing they've actually made or not (or am I just missing something super obvious?)
pcblues•9m ago
I hadn't thought of using git to track the changes in legislation. This is a cool idea.

In Australia, I spent a bit of time trying to work out how to find which politician voted for what (both at state and federal level), so that when elections come, you can single out the individuals who voted for what legislation. I think AI may make this easier, but the challenge is in not spamming the "free and open" access to the online record of our legislation.

So far, it's probably a one-person $50K per year job to do this task manually, and the language of the public legislation record didn't lend itself easily to determining the laws or rights that actually changed when bills were passed into legislation. They are explicitly stated, but hard to distill with regexes, filters or other analysis tools (e.g. "Who voted to stop electric scooters going over 25km/h?") If you try reading the legislation, you will know what I mean.

"A complete and open record of the proceedings of our parliament" still needs people spend a good chunk of time interpreting and summarising it (e.g. the media, commentators, etc) which means it's a time-consuming hobby or a paid gig.

Ericson2314•8m ago
The Hacker News Community (hah) needs to lobby hard to pass a law (what boostrapping!) to require the https://en.wikipedia.org/wiki/Office_of_the_Law_Revision_Cou... to maintain the repo as part of their duties, and do it retroactively for the entire history of the US Code.

It's a simple idea; it's cheap; there are no outstanding technical questions; it benefits almost everyone. Let's get this done.