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: "2.14.3 Released!"
date: 2021-04-08T00:00:00-00:00
replaces: []
---
After releasing Pidgin 2.14.2 some of our users which run Pidgin on Windows
reached out to us about them having issues with the installer. This release
takes care of this issue that affected Windows builds of Pidgin.
Also, this release removes the AIM protocol plugin. This is certainly an
interesting change considering that the Pidgin project started as a chat client
for AIM, yet it's important to remember that AIM was shutdown in December 2017
so this removal was long overdue.
The complete changelog for this release is the following:
libpurple:
* Removed the AIM protocol plugin. AIM has been shut down since December 15th
of 2017. We left it around because of a third party server, but our plugin no
longer works with it. ({{% review 598 %}}) (Gary Kramlich)
Windows:
* Standardize on wprintf in pidgin/win32/winpidgin.c ({{% review 593 %}}) (Gary Kramlich)
* Use the inetc nsis plugin that supports https ({{% review 593 %}}, {{% review
594 %}}) ({{% issue PIDGIN-17511 %}}) (Gary Kramlich)
* If building under msys2 copy libgcc_s_dw2-1.dll and libwinpthread to the
install directory. ({{% review 593 %}}) ({{% issue PIDGIN-17511 %}}) (Gary
Kramlich)
You can find 2.14.3 on
[SourceForge](https://sourceforge.net/projects/pidgin/files/Pidgin/2.14.3/).
We hope everyone enjoys this release and the fixes it brings. Remember that if
you have any questions or comments we have a [variety of channels]({{< ref
"contact" >}}) where you can reach out to us.