Georgios Kontaxis <firstname.lastname@example.org> wrote: > > Georgios Kontaxis via GitGitGadget <email@example.com> wrote: > >> Introduce an 'email-privacy' feature which redacts e-mail addresses > >> from the generated HTML content > > > Eric Wong wrote: > > A general reply to the topic: have you considered munging > > addresses in a way that is still human readable, but obviously > > obfuscated? > > > > On some other project, I settled on HTML "•" as a replacement > > for '.' for admins who enable that option. The $USER@$NO_DOT > > remains as-is for easy identification+recognition of hosts. > > > Thanks for the suggestion. > > People have been trying to hinder address harvesting for a while now. > Replacing '@' with "at", the dot with "dot", adding spaces, etc. > was pretty common at some point. May still be. > I would expect crawlers to have caught up and this includes > all sorts of character encodings and unicode look-alike substitutions. I figure the crawlers hit a combinatorial explosion and give up since they'd be wasting time with false-positives. > > I also considered Unicode homographs which can look identical > > to replacement characters, too; but rejected that idea since > > it would cause grief for legitimate users who would not notice > > the homograph when pasting into their mail client. As a data point, none of the homograph@ candidates I posted here on Mar 29 have attracted any attempts on my mail server.