[racket-dev] bug reporting system is not spam-protecting email addresses

From: Eli Barzilay (eli at barzilay.org)
Date: Mon Jun 27 14:08:19 EDT 2011

Oh, and if anyone can try scrape emails and sees some leftovers, I can
hunt them down too.

6 minutes ago, Eli Barzilay wrote:
> Changing gnats to do this sounded difficult (as in reqiuring me to
> learn enough perl), but the code turned out to be organized enough so
> this is implemented now.
> 1. The gnats script works as usual, except that every value that it
>    displays goes through the common simple regexp-replace-based
>    obfuscation.  The only emails left are unqualified ones that
>    correspond to foo at racket-lang.org emails.
> 2. Better: when there is a user that is logged in, the above is
>    disabled, so there's no problem with committing obfuscated
>    addresses.
> One nit: in the "audit trail" the obfuscation is "foo at bar.baz"
> instead of "foo at bar dot baz".  I can fix that if anyone tells me
> what's the perl equivalent of `regexp-replace' with a function.  (Or
> better, if anyone knows enough perl, I'll send you the code.)

          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!

Posted on the dev mailing list.