This would certainly annoy any automatic harvesting of your pages.
Or include "invisible" records (e.g. background and foreground color the same and very small point size) with good-looking but bogus information, which would then poison the harverster's database (although this will be bad for text-only browsers).
If you do not have to cater for text-only browsers, one can think of providing the data in XML-format with the tags being given random names for this page only (and of course a different sequence of field-tags within the record tags, with some unused fields tags thrown in for good measure, e.g. two addresses and two phone numbers for each record, one of which will only be rendered) and making a "this page only" XSLT-file which translates client-side the data into HTML. Modern browsers will translate the XML into HTML on the fly, but it will take a fairly sophisticated harvester to make sense of it (or a lot of post-processing the raw data).
CountZero
"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
In reply to Re: State-of-the-art in Harvester Blocking
by CountZero
in thread State-of-the-art in Harvester Blocking
by sgifford
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |