commit df9b3790817d4d64fee06e046a479a67d4a91b13
from: Omar Polo <op@omarpolo.com>
date: Mon May 02 18:48:40 2022 UTC

remove mentions of GPG, I stopped signing with it for a while already

commit - db48d276a7b1688dba7fe3272bb89ad8372ba7da
commit + df9b3790817d4d64fee06e046a479a67d4a91b13
blob - 44fd1acddc51ae1f1b391a67a6e6048c33833380
blob + 9309c370cd701084ea3bf9a1843f65a3fc01f848
--- site/index.gmi
+++ site/index.gmi
@@ -55,10 +55,9 @@ $ make
 $ sudo make install # eventually
 ```
 
-A SHA256 file is available.  However, that only checks for accidental corruption: you can use signify (SHA256.sig and the public key gmid-CURV.pub) or GPG.  The hash of the signify public key is also included in the SHA256 file and thus signed with my GPG.  The signify public key for the next release ‘gmid-NEXTV.pub’ is also included.
+A SHA256 file is available.  However, that only checks for accidental corruption: you can use signify (SHA256.sig and the public key gmid-CURV.pub).  The signify public key for the next release ‘gmid-NEXTV.pub’ is also included.
 
 => GITHUB/releases/download/VERS/SHA256		SHA256
-=> GITHUB/releases/download/VERS/SHA256		SHA256.gpg
 => GITHUB/releases/download/VERS/SHA256.sig	SHA256.sig
 
 To verify the signatures with signify(1)