I'm the boss! Please enjoy my finely curated links.
Golang @programming.dev Go 1.22: Interactive release notes
Espresso @infosec.pub DIY Espresso
Golang @programming.dev Unmasking a Go HTML Parser Bug with Differential Fuzzing
Golang @programming.dev WASI support in Go
Golang @programming.dev CGO Performance In Go 1.21
cybersecurity @infosec.pub CVE-2020-19909 Is Everything That Is Wrong With Cves
cybersecurity @infosec.pub Bypassing Bitlocker using a cheap logic analyzer on a Lenovo laptop
Golang @programming.dev Structured Logging with slog
cybersecurity @infosec.pub WinRAR flaw lets hackers run programs when you open RAR archives
Golang @programming.dev Backward Compatibility, Go 1.21, and Go 2
Espresso @infosec.pub Espresso Coffee Mitigates the Aggregation and Condensation of Alzheimer′s Associated Tau Protein
cybersecurity @infosec.pub Summary: MTE As Implemented
Golang @programming.dev What’s New in Go 1.21 Comprehensive Notes
cybersecurity @infosec.pub The Ups and Downs of 0-days: A Year in Review of 0-days Exploited In-the-Wild in 2022
Golang @programming.dev Scripting with Go: a 400-line Git client
Cryptography @lemmy.ml The Cryptographer Who Ensures We Can Trust Our Computers
Golang @programming.dev Go 1.22 inlining overhaul
Golang @programming.dev Common pitfalls in Go benchmarking






We're all trying to figure out where these headlines came from. The stable channel with all the fixes does not (at this time) bundle the warning. How is that users have become confused and believe the dev channel is the only way to get security fixes?