Longevity of IPFS content referenced in issues ( Github, Mailing lists, etc )

**NOTE**: This issue is **orthogonal / the opposite of** *github issues on IPFS*

A non-trivial portion of bugreports / issues / design documents currently available on github etc **do refer to IPFS file content** ( `Qm...` ). A staggering portion of **this content does not currently resolve**: either being lost for good or sitting on nodes not currently online. To make matters worse much of this content is a direct product of ProtocolLabs members, which has implications on the perceived health of the product.

Some sort of quick-and-dirty solution needs to be implemented as soon as feasible to systematically crawl and pin content across at least github issues/pulls, due to the high visibility of resolution failures.
There would be implications with potential for abuse of the pinning service / moderation evasion, but these should be dealt with as they arise, and not get in the way of "the simplest thing that can/should exist today"

/cc @VictorBjelkholm @Mr0grog @whyrusleeping