Radicle 1.0 – A local-first, P2P alternative to GitHub(radicle.xyz)

152 points by aiw1nt3rs 2 years ago | 39 comments

Radicle 1.6.0 – Amaryllis(radicle.xyz)

37 points by zdw 9 months ago | 9 comments

Radicle: Sovereign {code forge} built on Git(radicle.dev)

236 points by KolmogorovComp 5 months ago | 86 comments

SocketAddrV6 is not roundtrip serializable(sunshowers.io)

26 points by cyndunlop 11 months ago | 4 comments

Cloudflare's AI Psychosis(opensauce.it)

73 points by gregzeng95 2 months ago | 35 comments

PixieFail: Nine Vulnerabilities UEFI Implementations(blog.quarkslab.com)

141 points by weinzierl 2 years ago | 82 comments

Inside the "3 billion people" national public data breach(troyhunt.com)

540 points by bubblehack3r 2 years ago | 358 comments

Troy Hunt's blog post analyzing the National Public Data breach, which was claimed to expose records on 3 billion people.

A Vulnerability in Libsodium(00f.net)

323 points by raggi 10 months ago | 47 comments

Blog post by Frank Denis, libsodium's author, describing a vulnerability found in the libsodium cryptographic library.

There isn't an easy exploit for this PHP vulnerability(eliastaylor.com)

566 points by zkldi 4 days ago | 437 comments

Blog post arguing a newly disclosed PHP vulnerability is hard to exploit and that thousands of LLM-generated GitHub PoC exploits don't work against vanilla PHP.

Twelve years of distributed SQLite(philipotoole.com)

365 points by otoolep 2 days ago | 62 comments

Philip O'Toole's blog post recounting the history of distributed SQLite since he launched rqlite in 2014, covering dqlite, Litestream, LiteFS, libSQL/Turso, cr-sqlite and Cloudflare D1.

What Is PID 0?(blog.dave.tf)

344 points by todsacerdoti 2 years ago | 56 comments

Blog post by David Anderson explaining what PID 0 is in Unix/Linux, why it is hidden from userspace, and its role in booting and idle scheduling.

Vercel April 2026 security incident(bleepingcomputer.com)

817 points by colesantiago 6 months ago | 466 comments

Vercel security bulletin disclosing unauthorized access to certain internal systems in April 2026, affecting a limited subset of customers, with an ongoing investigation.