frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

France's homegrown open source online office suite

https://github.com/suitenumerique
258•nar001•2h ago•135 comments

British drivers over 70 to face eye tests every three years

https://www.bbc.com/news/articles/c205nxy0p31o
27•bookofjoe•24m ago•10 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
383•theblazehen•2d ago•138 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
67•AlexeyBrin•4h ago•13 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
753•klaussilveira•18h ago•234 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
44•onurkanbkrc•3h ago•2 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
1012•xnx•1d ago•573 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
118•alainrk•3h ago•131 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
145•jesperordrup•8h ago•55 comments

First Proof

https://arxiv.org/abs/2602.05192
16•samasblack•54m ago•11 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
11•vinhnx•1h ago•1 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
94•videotopia•4d ago•23 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
10•rbanffy•3d ago•0 comments

Making geo joins faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
148•matheusalmeida•2d ago•40 comments

Ga68, a GNU Algol 68 Compiler

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
30•matt_d•4d ago•7 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
255•isitcontent•18h ago•27 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
267•dmpetrov•19h ago•142 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
536•todsacerdoti•1d ago•259 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
412•ostacke•1d ago•105 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
355•vecti•20h ago•161 comments

What Is Ruliology?

https://writings.stephenwolfram.com/2026/01/what-is-ruliology/
59•helloplanets•4d ago•57 comments

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
12•sandGorgon•2d ago•2 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
328•eljojo•21h ago•198 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
452•lstoll•1d ago•297 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
366•aktau•1d ago•192 comments

Cross-Region MSK Replication: K2K vs. MirrorMaker2

https://medium.com/lensesio/cross-region-msk-replication-a-comprehensive-performance-comparison-o...
7•andmarios•4d ago•1 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
297•i5heu•21h ago•252 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
105•quibono•5d ago•32 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
55•gmays•13h ago•22 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1109•cdrnsf•1d ago•490 comments
Open in hackernews

So you want to serialize some DER?

https://alexgaynor.net/2025/jun/20/serialize-some-der/
76•lukastyrychtr•7mo ago

Comments

PeeMcGee•7mo ago
The post title is misleading and the content reads more like a guerilla advertisement for claude. TL;DR: author works for Anthropic, and used claude to implement an optimization for LLVM.
quentinp•7mo ago
He’s also well respected in the Python community for maintaining the cryptography package, partially written in Rust. This is just a random blog post, not an ad.
lmm•7mo ago
Maybe. But the fact they work for Anthropic is very relevant and changes my impression of the post quite a lot.
__alexs•7mo ago
FWIW Having worked a lot with Alex on cryptography he seems almost entirely incapable of doing something that I would normally consider an advert.

Sometimes people have good experiences with tools and like to share them.

brabel•7mo ago
The author has added a note in the beginning of the post now making it clear that he works for Anthropic, which may explain the fixation on Claude Code!
benmmurphy•7mo ago
having two very different code paths for measuring the length of the DER buffer and writing the DER sounds very scary. i guess its fine with Rust but the idea would give me the heebee-jeebies for any other language unless they are using a safe buffer implementation. i would find it hard to trust that there is no buffer overflow based on divergent behaviour between the two functions.
tptacek•7mo ago
This piece starts out super-duper inside baseball (optimizing DER encoding for, in the main, X.509 certificate handling) in Rust code that is increasingly leveraged by Python's cryptography stack. But it ends up somewhere crazy: with an LLM agent apparently one-shotting an LLVM optimization, then semiformally verifying the change, which is ultimately merged by the LLVM team.
ggm•7mo ago
So many encoding rules. DER, PER. It's an xkcd cartoon but inside one asn.1 standard!
dathinab•7mo ago
it's as much one standard as OIDC is ;)

(as in it isn't one standard but a group of standards, like asn.1 without any encoding is split in ~4 standards by itself. Through to be fair all or CER, BER and DER are in the same standard. But PER is another standard, so is XER, OER, JER, GSER, RXER each and others.)

jnwatson•7mo ago
The standard is 41 years old, so there has been plenty of time for extensions.

Practically, the useful encodings are DER, which is canonical and used for crypto, and XER, which is human-readable.

It is a neat spec, chock-full of great ideas. Unfortunately, given its age, there have been many bad implementations of it.

zzo38computer•7mo ago
> There’s only one encoding I choose to acknowledge, which is DER (the Distinguished Encoding Representation, it’s got a monocle and tophat).

I also prefer to use DER, because it is better than BER and CER. DER is actually a subset of BER but BER has some messiness which is avoided by DER; because there are not as any ways to encode data by DER this makes it simpler to handle.

DER is also the format used by X.509 certificates, so this is fortunate; however, I use DER for other stuff too (since I think it is generally better than XML, JSON, CSV, etc).

I wrote a library in C to serialize and deserialize DER.

NoahZuniga•7mo ago
DER encoding is in fact unique.
simonw•7mo ago
The most interesting part of this post is the bit about half way down, where Alex uses Claude to help identify a missing compiler optimization in LLVM... and then uses Claude Code to implement that optimization and gets a PR accepted to LLVM itself! https://github.com/llvm/llvm-project/pull/142869
CJefferson•7mo ago
I feel this is going to be the thing which really boosts automated theory proving.

Up until now it's always been a hard sell, people say "Well, I can prove it myself, and that's less work than getting the computer to prove it", and they weren't completely wrong.

However, now we have LLMs which can do lots of interesting work, but really can't be trusted for anything important (like an LLVM optimisation pass, for example). If those LLMs can convince a theorem prover the LLVM optimisation pass is correct, then suddenly their output is much more useful.

tialaramex•7mo ago
One concern here is that proofs don't necessarily prove what we intuitively think they do. So we need to be very careful to understand what we actually proved.

The TLS 1.3 "Selfie attack" is an example of a gap between what we did prove and what we intuitively understood.

The formal proof for TLS 1.3 says Alice talking to Bob gets all the defined benefits of this protocol, and one option is they have a Pre-shared Key (PSK) for that conversation. They both know the same key, in that sense it's symmetric.

But the human intuition is that we're talking about an Alice+Bob key, whereas the proof says this is an Alice->Bob conversation key. If we re-use the same PSK for Bob->Alice conversations too we get the Selfie Attack, the formal proof never said we can expect that to work, it was just our intuition which confused us.

GoblinSlayer•7mo ago
The article says the proof only considered session resumption PSK, and overlooked out of band PSK, which was left for future work. Maybe if they could have a list of features, but TLS is too complex for that.

Also PSK involves sending a PSK identity, which is supposed to be used to find the PSK, in particular it can be a user name, so the server can check the user name is correct.