>>>>> "CVR" == Chuq Von Rospach <firstname.lastname@example.org> writes:
CVR> On 8/1/02 2:49 PM, "Russ Allbery" <email@example.com> wrote:
>> If you do implement this, it would be cool if you could make it
>> a per-user option. My address is public. I want it that way.
>> I use it in the mailto links on my web pages and I use it when
>> posting to Usenet. I deal with the spam that results; I prefer
>> to be accessible.
CVR> I do that, also. Whether it's user-choosable, I dunno. But
CVR> one of the things that isn't currently being talked about
CVR> (nor, I think, should it be) is cloaking content, like
CVR> .sigs. So if it's in your .sig, it'll be public, no matter
CVR> what the list server does.
I don't have too much of a problem with that. People put their
contact information in their sigs because -- surprise -- they want to
be contacted. I think we tread on more questionable grounds when we
start munging content.
CVR> Would that be "good enough"?
OTOH (there's always a tangle of "other hands") content is a good
place to get your address leaked by others, usually inadvertently or
innocently. Check out the attribution above. I've just leaked Chuq's
email address. Of course, if it had been munged on the exploder side,
I would simply have leaked a munged address, but you're still
vulnerable to leakage in content.