Musings

I considered this.

But we are so far from having support for PGP-signed comments widely enough deployed for them to even come on the radar screen of the spammers, that I figure it’s not even worth worrying about at this point.

Right now, whether PGP-signed comments get rel="nofollowed" is a trivial little change to a single MT template module. The day I see a PGP-signed spam comment, I could change policies in less than a minute.

In the meantime (which could be a long time), it’s worth rewarding those who PGP-sign their comments.

A two-line change to the OpenPGPComment 1.5 plugin. The first line adds a new tag, <MTPGPCommentAuthorLink>; the second makes <MTPGPIfSigned> compatible with <MTElse> (a bugfix, really).

--- OpenPGPComment.pl.orig      Mon Mar 29 19:35:10 2004
+++ OpenPGPComment.pl   Fri Feb  4 23:51:55 2005
@@ -72,6 +72,7 @@
 MT::Template::Context->add_container_tag('IfNotSpecificComment' => sub{&showCommentForm;});
 MT::Template::Context->add_tag('PGPCommentBody' => sub{&_hdlr_pgpcomment_body;});
 MT::Template::Context->add_tag('PGPCommentPreviewBody' => sub{&_hdlr_pgpcomment_body;});
+MT::Template::Context->add_tag('PGPCommentAuthorLink' => sub{&MT::Template::Context::_hdlr_comment_author_link;});
 MT::Template::Context->add_conditional_tag('IfPGPSigned' => sub {&ifPGPSigned;});


@@ -162,6 +162,7 @@
 sub ifPGPSigned {
        my $ctx = shift;
        my $pgp_signed=0;
+       local $ctx->{__stash}{tag} = "PGPSigned";
        my $comment_text = $ctx->stash('comment')->text;
        my $q = CGI->new;
         my $raw_pgp=$q->param('raw_pgp');

Then a small change in template module to conditionally use <MTPGPCommentAuthorLink> or <MTCommentAuthorLink>, depending on whether the comment is signed.

It would be even cooler if you were to make your public key available from your homepage, as specified above.