Joe Pluta wrote:
create a new symbolic link in the IFS to the image for each
request, and then send that symbolic link name. You'd run
a regular job to clear out old links.
That's a pretty good idea, but every file has a "signature", so to
speak. A clever bot author wouldn't need to rely on a file name. And
remember that a learning bot would be downloading and duplicating your
entire image library and description cross-reference table, and could be
assigning its own name to the image. It would just need to match up the
signature. A signature might consist of a combination of factors such
as total # of bytes, plus various byte comparisons interspersed
throughout the stream.
It's not that I have a better idea. I don't, but wish I did. The
TicketMaster case kind of jarred me into the reality that a bot author
may have a strong financial interest in overcoming a captcha.
Nathan.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.