NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
Ovid
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Illegal? (Score:1)
The only reason you knew you weren't supposed to have that stuff is that you happened to see that they tried to stop you.
What if some other site links to the "protected" images? Would that be labled as "circumventing the security" and deemed illegal by DMCA or whatever that weird law is called?
Anything you get over HTTP without logging in... Like, welcome to the Web.
Hiring the right person . (Score:1)
Your tale is interesting, since it hilights a very common yet difficult to solve problem -- how does a customer without specialist knowledge tell if their tradespeople are properly skilled?
It's unlikely that the photographers themselves have a good knowledge of computer programming, so they have hired an external party to do the work. From a layperson's standpoint (who knows nothing of javascript, HTML, and computer security) the site looks and feels secure.
This isn't a problem that's restricted to