public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jsm AT cygnus -dot- com>
To: overseers AT sourceware.cygnus -dot- com
Subject: I'm back, change in web archives
Date: Mon, 13 Sep 1999 12:11:00 -0000	[thread overview]
Message-ID: <19990913121151.A14080@cygnus.com> (raw)

I'm back from vacation.

After a week off, I have a huge pile of incoming mail to read, so
naturally I decided to blow it all off for an hour or two and fix a
long-standing TODO for the sourceware site.

The web archives are now a little more resistant to spam harvesters.
E-mail addresses are no longer listed in the subject and author indexes
(just the full name of the poster), and e-mail addresses in message
headers are modified with an expression like s,@, AT ,;s,.com, -dot-
com,; cygwin@sourceware.cygnus.com becomes cygwin AT sourceware.cygnus
-dot- com.

It's ugly, I know.  I'm open to better ideas.  I don't know if it's
worth the trouble of the second ".com, -dot com," substitution.

e-mail addresses in the body of messages are untouched.

The big web archive services on the net like www.egroups.com and
www.mail-archive.com go much farther than I have.  mail-archive.com
omits e-mail addresses in headers altogether.  egroups.com changes the
last character in the local part to a "-" and provides a link that you
can follow to get the correct address if you're a registered member.
(at least that's what it looks like the link does--I'm not a registered
member).


My change is not too effective if the harvester is clever enough to
write a regular expression fashioned to my particular rewrite rules.
I don't want to resort to destructively modifying the addresses like
these other sites have done, unless I really really have to.

Jason // Sourceware Czar
         Free the Software!

                 reply	other threads:[~1999-09-13 12:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990913121151.A14080@cygnus.com \
    --to=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).