Heartbleed is not super descriptive to layfolk but it's certainly catchy, I'll give you that. Having a dot-com domain with said simple name was great, too. But

Heartbleed is not super descriptive to layfolk but it's certainly catchy, I'll give you that. Having a dot-com domain with said simple name was great, too. But the content? A loud reminder indeed. As a member of the dev community, I would have wanted to see the following: 1. How bad is it? If you're using SSL, then an attacker may be able to read your machine's memory without leaving a trace. 2. Who is affected? Users of OpenSSL versions X-Y. Check your site here [http://filippo.io/Heartbleed/ http://filippo.io/Heartbleed/], but your client code may be affected too! 3. How do I secure myself? Update to OpenSSL version Z, reboot, and consider resetting all sensitive data on your server (reissue your SSL certificate, reset your user passwords and sessions, etc). These facts are littered throughout a 2,000+ word document. In the future, I would like to see these things answered plainly at the very top.