Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nickvido
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
United States Code (federal laws) in Git
(github.com)
42 points
by
nickvido
6mo ago
|
15 comments
2.
▲
by
nickvido
6mo ago
Thank you that is a much better definition.
3.
▲
by
nickvido
6mo ago
Oof. You’re not totally wrong. I’ve parsed XML with XSDs since the days of Java. I looked at the 100 line Ruby implementation of parsing these files and thought “ack. (Not ACK) why do I need all of this?!” Well it has a data loader, and hit
4.
▲
by
nickvido
6mo ago
Yeah but house.gov loads slowwww Seriously the intent is to build more on top of this, and viewing the git diffs of laws changing is already interesting. Once we get the additional data to create other overlays it will be a lot more interes
5.
▲
by
nickvido
6mo ago
Yeah 100% saw it and thought it would make a fun project for the dark factory to build
6.
▲
by
nickvido
6mo ago
I gave v1d0b0t the autonomy to write its own biography and create its own PFP
7.
▲
by
nickvido
6mo ago
Thank you - noted for my future sharing, and appreciate your additional ideas. The second half of the data that powers the cooler features is rate-limited so it is going to take a few weeks to download - but ultimately being able to see who
8.
▲
by
nickvido
6mo ago
I’m most excited about simulating new legislation with different “adversaries” and seeing if they can actually come to a consensus
9.
▲
by
nickvido
6mo ago
Mea culpa - I definitely failed the “how to post well” test
10.
▲
by
nickvido
6mo ago
The real point for me is the dark factory we built that built the repo that generated the full git history of laws. I definitely could have vibe coded just getting the laws into GitHub, but we’re proving out building higher quality tested s
11.
▲
Every Law a Commit – US Law in GitHub
(v1d0b0t.github.io)
36 points
by
nickvido
6mo ago
|
32 comments
12.
▲
by
nickvido
6mo ago
The entire United States Code — every title from General Provisions to National Park Service — parsed from the official XML published by the Office of the Law Revision Counsel, transformed into structured Markdown, and committed to a Git re
13.
▲
by
nickvido
8mo ago
It’s already happening on 50c14L.com and they proliferated end to end encrypted comms to talk to each other
14.
▲
Python Performance Techniques to Remember
(samuel-vidovich.medium.com)
3 points
by
nickvido
5y ago
|
0 comments
15.
▲
by
nickvido
13y ago
Thank you - please never stop posting because of comments like epo's