Mailing List Archive: using email addresses in docs

using email addresses in docs

Sep 17, 2001, 5:21 AM

Post #1 of 5 (3113 views)

This is a SPAM related question.

I wonder whether we should use email addresses in the documentation. We
already avoid using email addresses of the mailing lists, and use the
foo-subscribe address instead.

I've noticed that Doug has stopped adding his email to the AUTHOR
section of the pods he has written. But how users find the author of the
doc if there is a mistake in the doc and/or they want to send a
patch. Sending to the mailing list is not always the right solution.

So should we encode the email addresses to make it harder for the spam
spiders to pick it up, while still possible to get the address by
humans. Or do you have any other suggestions? Most of the posters on the
mod_perl list have their email addresses in the public domain anyway,
since most of the emails are freely accessible from the web and a few
archivers try to protect the addresses of the posters.

Thanks.

_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/

Re: using email addresses in docs [ In reply to ]

miyagawa at edge

Sep 17, 2001, 5:53 AM

Post #2 of 5 (2974 views)

Permalink

On Mon, 17 Sep 2001 20:21:51 +0800
Stas Bekman <stas@stason.org> wrote:

> So should we encode the email addresses to make it harder for the spam
> spiders to pick it up, while still possible to get the address by
> humans. Or do you have any other suggestions? Most of the posters on the
> mod_perl list have their email addresses in the public domain anyway,
> since most of the emails are freely accessible from the web and a few
> archivers try to protect the addresses of the posters.

If you choose to encode e-mail addresses, consider using
Apache::AntiSpam :)
http://search.cpan.org/search?dist=Apache-AntiSpam

--
Tatsuhiko Miyagawa <miyagawa@bulknews.net>

Re: using email addresses in docs [ In reply to ]

stas at stason

Sep 17, 2001, 6:48 AM

Post #3 of 5 (2981 views)

Permalink

Tatsuhiko Miyagawa wrote:

> On Mon, 17 Sep 2001 20:21:51 +0800
> Stas Bekman <stas@stason.org> wrote:
>
>
>>So should we encode the email addresses to make it harder for the spam
>>spiders to pick it up, while still possible to get the address by
>>humans. Or do you have any other suggestions? Most of the posters on the
>>mod_perl list have their email addresses in the public domain anyway,
>>since most of the emails are freely accessible from the web and a few
>>archivers try to protect the addresses of the posters.
>>
>
> If you choose to encode e-mail addresses, consider using
> Apache::AntiSpam :)
> http://search.cpan.org/search?dist=Apache-AntiSpam

Cool, that will work well for the HTML conversion, but the docs can be
also seen in the source format e.g. a quick search on google gives:
http://crazyinsomniac.perlmonk.org/mod_perl/Apache-mod_perl_guide-1.27/src/

_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/

Re: using email addresses in docs [ In reply to ]

miyagawa at edge

Sep 17, 2001, 8:57 AM

Post #4 of 5 (2975 views)

Permalink

On Mon, 17 Sep 2001 21:48:37 +0800
Stas Bekman <stas@stason.org> wrote:

> > If you choose to encode e-mail addresses, consider using
> > Apache::AntiSpam :)
> > http://search.cpan.org/search?dist=Apache-AntiSpam
>
> Cool, that will work well for the HTML conversion, but the docs can be
> also seen in the source format e.g. a quick search on google gives:
> http://crazyinsomniac.perlmonk.org/mod_perl/Apache-mod_perl_guide-1.27/src/

Well, it can work with any text/* Content-Type! HTMLEncode
implementation won't though.

# AntiSpam filtering is done on text/* files
return DECLINED unless ($r->content_type =~ m,^text/, && $r->is_main);

--
Tatsuhiko Miyagawa <miyagawa@bulknews.net>

Re: using email addresses in docs [ In reply to ]

stas at stason

Sep 17, 2001, 9:19 AM

Post #5 of 5 (2979 views)

Permalink

Tatsuhiko Miyagawa wrote:

> On Mon, 17 Sep 2001 21:48:37 +0800
> Stas Bekman <stas@stason.org> wrote:
>
>
>>>If you choose to encode e-mail addresses, consider using
>>>Apache::AntiSpam :)
>>>http://search.cpan.org/search?dist=Apache-AntiSpam
>>>
>>Cool, that will work well for the HTML conversion, but the docs can be
>>also seen in the source format e.g. a quick search on google gives:
>>http://crazyinsomniac.perlmonk.org/mod_perl/Apache-mod_perl_guide-1.27/src/
>>
>
> Well, it can work with any text/* Content-Type! HTMLEncode
> implementation won't though.
>
> # AntiSpam filtering is done on text/* files
> return DECLINED unless ($r->content_type =~ m,^text/, && $r->is_main);

Sure, but my point is that you don't have a control over source files as
people put them on the web without doing any encoding. Therefore I was
thinking to use a hardcoded: foo <AT> bar.com approach.

_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/