@sizzlemctwizzle <tt>.getElementsByTagName("a")</tt> returns a list of all <tt>A</tt> elements, including anchors, and so will generate an error when it encounters an anchor that has no href property (though it may be that all A tags have a href property in the DOM). If you use <tt>document.links</tt> you get only links with an href. But you are right, <del>there is no "links" tag so the script will fail</del> (well I guess it took me 25 minutes to compile this). But then if you use xPath you can get an html collection that only contains rapidshare links, and so you could eliminate the regexp or have it do something more useful. @john34516 I already made a <a href="http://userscripts.org/scripts/show/13709">script for this</a>, which you would certainly find if you did a search, and you could comment in that script's section. It will not download the entire file (or even the error page) as would psyched's example in certain cases. I have heavily tested it and it works well, but with a couple problems yet - A large number of bad links (perhaps over 150, I'm not sure) will get your IP (apparently) blocked. I have figured out a fix for this. The script really only looks for good links, it isn't really designed to analyze bad links, I only need to know if a link is good. Sometimes a server is down or isn't responding, this doesn't mean the file is gone, and I'm not sure if there's anything JavaScript can do about it since the timeout period is so long. The script wouldn't post an edit to the forum, but I'm sure it could be patched to do so. <strong>However</strong>, this is not the right way to do that, you'd be much better off with a server-side script to do the checking, it would be much faster and more reliable. I have talked to a forum moderator that uses one of these, and he was only using my script when for some reason the server-side script wasn't working. <p>@sizzlemctwizzle <br /><tt>.getElementsByTagName("a")</tt> returns a list of all <tt>A</tt> elements, including anchors, and so will generate an error when it encounters an anchor that has no href property (though it may be that all A tags have a href property in the DOM). If you use <tt>document.links</tt> you get only links with an href. But you are right, <del>there is no "links" tag so the script will fail</del> (well I guess it took me 25 minutes to compile this). But then if you use xPath you can get an html collection that only contains rapidshare links, and so you could eliminate the regexp or have it do something more useful.</p> <p>@john34516 <br />I already made a <a href="http://userscripts.org/scripts/show/13709">script for this</a>, which you would certainly find if you did a search, and you could comment in that script's section. It will not download the entire file (or even the error page) as would psyched's example in certain cases. I have heavily tested it and it works well, but with a couple problems yet - A large number of bad links (perhaps over 150, I'm not sure) will get your IP (apparently) blocked. I have figured out a fix for this. The script really only looks for good links, it isn't really designed to analyze bad links, I only need to know if a link is good. <br />Sometimes a server is down or isn't responding, this doesn't mean the file is gone, and I'm not sure if there's anything JavaScript can do about it since the timeout period is so long. <br />The script wouldn't post an edit to the forum, but I'm sure it could be patched to do so. <br /><strong>However</strong>, this is not the right way to do that, you'd be much better off with a server-side script to do the checking, it would be much faster and more reliable. I have talked to a forum moderator that uses one of these, and he was only using my script when for some reason the server-side script wasn't working.</p> 2007-12-29T22:19:40Z 2 Forum 5700 1501 2007-12-29T22:26:41Z 27110