It has been corrected since then - the post is from February 28th, not sure why it's just now hitting HN.

This isn't a real-time complaint.