Hi,
Hiding the changed: lines definitely breaks every system that keeps _copies_ of the entries because it is impossible to update entries from these copies without trashing the existing entries.
I do not understand that one.
If you don't know the changed: lines you cannot update them correctly. The only possible update is one with newly generated changed lines that trash existing changed lines. Of course you could change semantics and merge delivered changed lines with those hidden in the database (or always use the address from the mail headers which might be a problem for people sending updates by a robot). Then you have to invent a new method to delete changed lines (which is currently possible and sometimes needed to correct bad data). In any case, this change _will_ break scripts.
And if you make the changed: line availables optionally then those who want to use addresses will quickly figure out how to get them.
Gabor's argument was about users with no clue (or scripts) finding addresses in output returned by whois. This would be prevented.
At least they do in my experience users with no clue do not write scripts. Instead they use scripts created by others.
Also we can add the usage of this flag to our heuristics which detect patterns in whois queries.
If you cannot rely on being presented all data you cannot use the data. If your heuristic sometimes presents the changed: lines and sometimes not (otherwise it wouldn't be a heuristic) we better drop the changed: lines (and all included information) altogether. Not that I or our customers would like this. Greetings, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster@xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ]