Top all-time · #13208
Stefan Eissing
Personal blog · eissing.org/icing/postsprogrammingsystems
Stefan Eissing writes icing's blog, a personal blog at eissing.org about programming and systems. Since 2025, 5 different Hacker News readers have linked it 6 times. It is still writing: the last post was on 2026-07-28, and you can follow it by feed.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link Stefan Eissing's posts on curl and libcurl internals, including a write-up on using Apple's SecTrust with curl and on libcurl's handling of thread cancellation in glibc.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
What Hacker News says?
Apple can fix this by building curl with SecTrust [1]. [1] https://eissing.org/icing/posts/curl-apple-sectrust/
Comment linking /icing/posts/curl-apple-sectrust/
on “Apple's git still trusts the compromised eMudhra certificates”Submitted RIP pthread_cancel as a story · 238 points
HN discussionlibcurl dealt with this a few months ago, and the sentiment is about the same: thread cancellation in glibc is hairy. The short summary (which I think is accurate) is that an hostname query via libnss ultimately had to read a config file, and glibc's `open` is a thead cancellation point, so if it's canceled, it'll won't free memory that was allocated before the `open`. The write-up is on how they're dealing with it…
Comment linking /icing/posts/pthread_cancel/
on “How to stop Linux threads cleanly”Submitted Curl Rate Limits as a story · 2 points
HN discussionSubmitted Curl Bitsets as a story · 1 points
HN discussionSubmitted curl DNS 2026, part IV, threads as a story · 1 points
HN discussion