How about wiping email addresses from the mails, but providing a link
under the author's name that would fetch a re-written version of the
address into a small window e.g. (01)
@# joe
!# @
+# sixpack.
&# org (02)
and display it (with those line-start chars being jumbled around).
It might not be too hard to generate random noise around the address. (03)
as9d8f7f0a987fd6joe8asd98fas09f87
asd987a08f7t@7a0ds987a0ds87sadf70
salkfjadsf987fsd4sixpack.ea0s9f70
09a87f098asd0973org3asd8708asd07a (04)
But paint the address terms a different colour from the rest of the
text. Not sure how to cater for accessibility though... (05)
Thoughts? (06)
--
Peter (07)
On 7 Jul 2004 at 22:20, Eugene Eric Kim wrote: (08)
> On Wed, Jul 07, 2004 at 08:54:56PM -0700, Jack Park wrote:
>
> > OTOH, there are still people who use email clients which
> > thoughtlessly (though presumed to be helpful) put the whole damned
> > return address back into the body, as if:
> >
> > JoeSixpack at joe@sixpack.org recently stated:...
>
> Not a problem. We can write a filter that obscures addresses within
> the message body as well.
>
> The plan right now is:
>
> * Archives are publically available, except the email addresses in
> both the headers and body are obscured.
>
> * Email addresses are unobscured when people log into the system.
>
> I'm not crazy about this, because there are often legitimate reasons
> for wanting to know someone's email addresses from an archived
> message, and having to have an account to get access seems lame. Then
> again, our support for e-names will make this far more acceptable.
>
> -Eugene
>
> --
> This message is archived at:
>
> http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=20040708052
> 007.GC16914@douge.blueoxen.net
> (09)
--
This message is archived at: (010)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=40ED9CC5.3603.398179@localhost (011)
|