Ladies and Gentlemen, here it is. We’ve put a lot of effort into this, and it’s very long. We tried to think of every angle in terms of privacy, and the effort was worth it. Almost 13,000 words about how to protect your privacy online. There’s no need to read it at once, just check the index below and click on the parts that interest you.

C++11 and 14 provide a tool that expresses single ownership of a resource, unique_ptr. When the unique_ptr is deleted, such as when its parent container is destroyed or when it goes out of scope, a custom deleter can be called instead of the delete operator. This behavior is exactly the right mix for managing a resource created by a C library.

An example of a typefree printf with variadic templates: http://en.cppreference.com/w/cpp/language/parameter_pack#Example

There are many classic tech debates, and the question of what to formally call web addresses is one of the most nuanced. The way this normally manifests is someone asks for the "URL" to put into his or her browser, and someone perks up with,

Actually, that's called a URI, not a URL...

The response to this correction can range from quietly thinking this person needs to get out more, to agreeing indifferently via shoulder shrug, to removing the safety clasp on a Katana. This page hopes to serve as a simple, one page summary for navigating the subtleties of this debate.

compile c/c++ code in assembly with an broswer

Lots of useful bash scripting tips:

$? exit status of the last command (${PIPESTATUS} for pipelined commands)

avoid tempory files:
diff <(wget -O - url1) <(wget -O - url2)

vm based distribution

snowflake generator (particle bomberman ?)

Sumo techniques

C++ is the main development language used by many of Google's open-source projects. As every C++ programmer knows, the language has many powerful features, but this power brings with it complexity, which in turn can make code more bug-prone and harder to read and maintain.

The goal of this guide is to manage this complexity by describing in detail the dos and don'ts of writing C++ code. These rules exist to keep the code base manageable while still allowing coders to use C++ language features productively.

And why it has been possible to exploit this: http://article.gmane.org/gmane.os.openbsd.misc/211963
xkcd: http://xkcd.com/1354/
history: http://www.smh.com.au/it-pro/security-it/heartbleed-disclosure-timeline-who-knew-what-and-when-20140414-zqurk.html