Top all-time · #5228
kivikakk.ee
Personal blog · kivikakk.eeprogramminghardware
kivikakk.ee is a personal blog at kivikakk.ee about programming and hardware. Since 2013, 15 different Hacker News readers have linked it 24 times, most often “Breaking homegrown crypto”. It is still writing: the last post was on 2026-10-09, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link kivikakk.ee for its write-up of a GitHub contribution-calendar pixel art project (Contrigraph), a recreation of the GitHub t-shirt. It is also cited in a discussion of security advice.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
hewwo
Most-linked posts?
- Breaking homegrown crypto9 people · 10 mentions · first linked 2016-02-20
- Being sorta useful in vim2 people · 2 mentions · first linked 2014-04-19
- /2013/05/07/contrigraph.html2 people · 2 mentions · first linked 2013-05-21
What Hacker News says?
There has to be a middle ground between saying "security is simple" and "the sky is falling". I think stating things like "don't trust user input" risks things like https://kivikakk.ee/cryptography/2016/02/20/breaking-homegro... happening. Security is hard, programming is hard, we should all get better at both.
Comment linking /cryptography/2016/02/20/breaking-homegrown-crypto.html
on “Data is a Toxic Asset”Submitted Breaking homegrown crypto as a story · 282 points
HN discussionAt this point I'll point out my recreation of the GitHub t-shirt: https://github.com/contrigraph And the write-up: http://kivikakk.ee/2013/05/07/contrigraph.html
Comment linking /2013/05/07/contrigraph.html
on “Pixel art for your Github contribution calendar”Submitted Breaking homegrown crypto as a story · 16 points
HN discussion> Look, you can't put up a blog post titled "How We Engineered CMS Airship to Be Simply Secure" and say that when asked "well, how did you actually engineer it to be secure?". In your post you talk about problems all solved by a framework, and apparently you haven't even evaluated what is out there already and rushed headfirst into building it all yourself. I've looked at Laravel, about two years ago. http://seclist…
Comment linking /cryptography/2016/02/20/breaking-homegrown-crypto.html
on “How We Engineered CMS Airship to Be Simply Secure”Submitted Erlang is slow: and other rubbish as a story · 13 points
HN discussionThis one's based on the Github tshirt: https://github.com/contrigraph See http://kivikakk.ee/2013/05/07/contrigraph.html
Comment linking /2013/05/07/contrigraph.html
on “The proper way to contribute on Github”Submitted Snapchat: not for state secrets as a story · 11 points
HN discussionSubmitted Breaking homegrown crypto as a story · 6 points
HN discussionSubmitted Breaking homegrown crypto as a story · 4 points
HN discussionSubmitted Breaking homegrown crypto as a story · 4 points
HN discussionSubmitted Python Still Surprises as a story · 3 points
HN discussionSubmitted Breaking CodeIgniter's homegrown crypto as a story · 2 points
HN discussionSubmitted Breaking homegrown crypto as a story · 2 points
HN discussionSubmitted Being sorta useful in vim as a story · 2 points
HN discussionSubmitted Erlang is slow: and other rubbish as a story · 2 points
HN discussionSubmitted Inefficiencies: using C++ and the Sapir–Whorf hypothesis as a story · 2 points
HN discussionSubmitted Chisel and C++, Together at Last as a story · 1 points
HN discussionSubmitted Breaking Homegrown Crypto (2016) as a story · 1 points
HN discussionSubmitted Inkplate Done Quick as a story · 1 points
HN discussionSubmitted Escapology: How, when and why to encode and escape as a story · 1 points
HN discussionSubmitted DTB Parser Implementing Notes as a story · 1 points
HN discussionSubmitted Being sorta useful in vim as a story · 1 points
HN discussionSubmitted Escapology: how, when and why to encode and escape as a story · 1 points
HN discussion