12th December 2005, 10:40 PM
It's what every player I've met has done over and over again when they "started gaming" all those yars ago (yars is BETTER than years).
But, it's a pretty bad pun...
And all one needs to do, if they must, is copy the link and put it in their address bar. Then it works fine. If you just click on it, you get one of those error pages that seem to be generated in ANGER for DARING to "leech" from some server.
Weltall, so you know, very often the original poster of a "leech protected" image won't be able to tell until they clear their cache, because the file they want people to see is still in their own cache and that's what the computer will prefer to use rather than going back online to download it again.
Come to think of it, by what means do they do this "leech protection" anyway? I mean, how exactly is typing the direct link to the file able to get around clicking on a link in some random forum? Does the average browser actually tell the server how it got there? Does the average browser send a signal that basically says "used a hyperlink" or "was embedded in HTML"? How silly. Such a message seems a tad risky. Shouldn't any request for a file appear exactly the same to the server? They should really just make clicking on a link send the same data to a server as typing it into the address bar. I see no logical reason to do otherwise.
But, it's a pretty bad pun...
And all one needs to do, if they must, is copy the link and put it in their address bar. Then it works fine. If you just click on it, you get one of those error pages that seem to be generated in ANGER for DARING to "leech" from some server.
Weltall, so you know, very often the original poster of a "leech protected" image won't be able to tell until they clear their cache, because the file they want people to see is still in their own cache and that's what the computer will prefer to use rather than going back online to download it again.
Come to think of it, by what means do they do this "leech protection" anyway? I mean, how exactly is typing the direct link to the file able to get around clicking on a link in some random forum? Does the average browser actually tell the server how it got there? Does the average browser send a signal that basically says "used a hyperlink" or "was embedded in HTML"? How silly. Such a message seems a tad risky. Shouldn't any request for a file appear exactly the same to the server? They should really just make clicking on a link send the same data to a server as typing it into the address bar. I see no logical reason to do otherwise.
"On two occasions, I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able to rightly apprehend the kind of confusion of ideas that could provoke such a question." ~ Charles Babbage (1791-1871)