Randomness is good and an extra space or two inserted randomly (e.g. spambait @ somedomain.com) might help (I don't think it says that the email address has to be machine-readable anywhere...)
m2 At 04:16 PM 5/29/2002, RWR wrote: >I think a more interesting question is what is the value of having >predictable output? > >The reason I ask is that one of the anti-harvesting strategy that we've >contemplated is a randonly generated output (ie - sometimes with comma's, >sometimes not, sometimes admin up top, sometimes down below)...etc... > >If predictability is highly valued, then I'd like to hear more... > >Hrm... > >-rwr > >----- Original Message ----- >From: "Charles Daminato" <[EMAIL PROTECTED]> >To: "Christopher Hicks" <[EMAIL PROTECTED]> >Cc: "OpenSRS dev-list" <[EMAIL PROTECTED]> >Sent: Wednesday, May 29, 2002 3:31 PM >Subject: RE: whois changes > > > > Well, they changed... > > > > Not sure what to say about that. It's not our policy to announce whois > > changes, it's a public service that's offered by mandate, and it's "take >it > > as it is" > > > > Hrm... > > > > Charles Daminato > > OpenSRS Product Manager > > Tucows Inc. - [EMAIL PROTECTED] > > > > > -----Original Message----- > > > From: Christopher Hicks [mailto:[EMAIL PROTECTED]] > > > Sent: May 29, 2002 3:29 PM > > > To: Charles Daminato > > > Cc: OpenSRS dev-list > > > Subject: RE: whois changes > > > > > > > > > On Wed, 29 May 2002, Charles Daminato wrote: > > > > Registrar of Record is by ICANN requirement: > > > > http://www.icann.org/registrars/ra-agreement-17may01.htm#3.3 > > > > Specifically line item 3.3.1.3: > > > > 3.3.1.3 The identity of Registrar (which may be provided through > > > > Registrar's website); > > > > > > Petty bureaucrats. Sheesh. > > > > > > > As for the comma, afaik that was always there *hrm....* > > > > > > Nope. I can show you diff's of whois from yesterday morning and this > > > morning for the same domain which has had no changes of any sort. > > > > > > -- > > > </chris> > > > > > > There are two ways of constructing a software design. One way is to make > > > it so simple that there are obviously no deficiencies. And the other way > > > is to make it so complicated that there are no obvious deficiencies. > > > - - C.A.R. Hoare > > > > >
