pidgin/nest

Add pgp public key and refer to it in our security disclosure method

The idea behind this is to make sure people that choose to use email to let us
known about a potential security issue in Pidgin encrypt the content of the
emails using a set of pgp keys of trusted Pidgin developers. For now we only
have the pgp key of grim but more keys can easily be added later on.

At the same time, since Hugo does not currently have a built-in shortcode for
linking directly to static resources, I had to add a new shortcode for doing so

Testing Done:
Ran `dev-server.sh` and made sure content looked as intended and links worked.

Bugs closed: NEST-46

Reviewed at https://reviews.imfreedom.org/r/860/
---
title: "Bintray Sunsetting"
date: 2021-02-04T22:13:17-06:00
replaces: []
---
Today [JFrog](https://jfrog.com) announced that they will be sunsetting
Bintray. You can read the announcement
[here](https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/).
Overall this doesn't affect us too much, but this does mean that we will be
relying on [SourceForge](https://sourceforge.net) for our downloads going
forward. Also, we have updated previous articles that were pointing to Bintray
to mention this update.
A few ideas have been thrown around like using [IPFS](https://ipfs.io/), but
due to our current timelines we can't afford to spend a lot of time
investigating and deploying new solutions. If you would like to help in this
regard please contact us!