Userscripts.org

Sorry to tell you that the Rapidshare Greasemonkey script works only partly for me. On the first screen the "Free" button is pressed automagically. The second page appears immediately with the final link. But when I press it, a remotely generated javascript error message appears. So I think Rapidshare is simply smart enough to defeat a premature download. My suggestion is to try to catch the javascript variable with the delay time and to download the file after that time elapsed.

I had concidered that as an option the first time it occured to me. However, i've noticed that if I just wait two to three seconds or so, I can get the file 'early', at least, earlier than the god awful 50 seconds it used to tell me to wait. Mostly I middle click everything anyway, so really the main motivation was to skip that damned 'free / premium' page automagicly, and I added the 'instant download' as a bonus, which isn't really instant :)

Perhaps I should do some testing and figure out the shortest delay (5s, probably), or I could read in the javascript variable. The only problem I see with auto-download is the following scenario:

1. you click a rapidshare link
2. page goes to rapidshare dl page
3. 5 seconds later, it downloads.

If you not, 2 into 3 is model, in that you cant do anything else. Thus, I usually do this:

1. 1. you /middle/ click a rapidshare link, and it opens in the background
2. 2. page goes to the rapidshare dl page
3. 3. when i remember to check my tabs, i click download :)

I could make it automatic, but the problem would then be the dialog that pops up after a (seemingly random) amount of time, inturrupting your train of thought on another tab. In additon, the tab wouldn't auto-close, so it'd just clutter the bar anyway.

If you can think of a solution to some of this, i'd be glad to hear it.

> Sorry to tell you that the Rapidshare Greasemonkey script works only partly
> for me. On the first screen the "Free" button is pressed automagically. The
> second page appears immediately with the final link. But when I press it, a
> remotely generated javascript error message appears. So I think Rapidshare is
> simply smart enough to defeat a premature download.
> My suggestion is to try to catch the javascript variable with the delay time
> and to download the file after that time elapsed.

Response:

I had concidered that as an option the first time it occured to me. However, i've noticed that if I just wait two to three seconds or so, I can get the file 'early', at least, earlier than the god awful 50 seconds it used to tell me to wait. Mostly I middle click everything anyway, so really the main motivation was to skip that damned 'free / premium' page automagicly, and I added the 'instant download' as a bonus, which isn't really instant :)

Perhaps I should do some testing and figure out the shortest delay (5s, probably), or I could read in the javascript variable. The only problem I see with auto-download is the following scenario:

1. you click a rapidshare link
2. page goes to rapidshare dl page
3. 5 seconds later, it downloads.

If you not, 2 into 3 is model, in that you cant do anything else. Thus, I usually do this:

1. you /middle/ click a rapidshare link, and it opens in the background
2. page goes to the rapidshare dl page
3. when i remember to check my tabs, i click download :)
I could make it automatic, but the problem would then be the dialog that pops up after a (seemingly random) amount of time, inturrupting your train of thought on another tab. In additon, the tab wouldn't auto-close, so it'd just clutter the bar anyway.

If you can think of a solution to some of this, i'd be glad to hear it. I'll post this as a comment on the script also.

sorry mee, moved it to a more public area now.

good to know - i used JS object detection but i wasnt sure if I did it right :)

I guess fail safe code really /can/ fail safely.