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: Sametime
date: 2019-08-07T22:48:49.000Z
replaces: []
weight: 50
lastmod: 2019-08-22T02:35:41.000Z
---
### Are there any public Sametime servers?
Apart from a demonstration server hosted by Lotus/IBM, no. This protocol is
designed to connect to a Lotus/IBM Sametime server running on a corporate LAN.
### Why doesn't Sametime appear in the protocols list?
Sametime support in Pidgin depends on a separate library called Meanwhile. You
will need to install the Meanwhile library and the `libpurple-meanwhile` (or
similar, depending on distribution) package to enable Sametime support. If you
are building Pidgin from source, then the Sametime plugin will be built
automatically if you have the development headers for Meanwhile installed.
### Why do I get the error "Not Authorized" when connecting?
The Sametime server to which you're attempting to connect has been configured
with a whitelist of acceptable clients. This error indicates that the client ID
used by Pidgin (`0x1700`) is apparently not in that whitelist, so the server
denies your login. You can cause Pidgin to masquerade as the default Sametime
Connect client by setting the "Hide client identity" option in your account
preferences.