Support for Galleries over 1000

[Gatekat]

Whether it is in one shot or the ability to include what page number/submission range to download, it would be very nice. It the largest galleries that I'm going to want to use this the most for.

[4pr0n]

1. There's already support for this

Run your own instance and edit this line: basesite.py#L14

If it means that much, you can pay someone to clone this project onto a private server & edit this line.

2. When the ripper first started, people were ripping tumblrs with 30,000 images and using up tons of API requests, disk space, and bandwidth. The original 500 image-cap was to curb the leechers. I bumped it up to 1000 since I myself found some sets slightly above 500. I can't find any sets that are > 1,000 that are actually "sets" and not just "random picture dumps".

Leaving open so others can see why the cap is set & that the cap is not going to be increased.

[Gatekat]

1. Thank you.
2. Of the ones I've run into so far:
   http://dcjosh.deviantart.com
   http://batchix.deviantart.com
   http://Casperium.deviantart.com
   http://Darkenlite.deviantart.com

Some artists do create quite the gallery after a few years.
I completely understand the limitation however.

This project is a wonderful thing.

On 8/23/2013 8:50 AM, 4pr0n wrote:

*There's already support for this*

Run your own instance and edit this line: basesite.py#L14
<https://github.com/4pr0n/rip/blob/master/sites/basesite.py#L14>

If it means that much, you can pay someone to clone this project onto a
webserver & edit this line.

1. When the ripper first started, people were ripping tumblrs with
   30,000 images and using up tons of API requests, disk space, and
   bandwidth. The original 500 image-cap was to curb the leechers. I
   bumped it up to 1000 since I myself found some sets slightly above
   1. I can't find any sets that are > 1,000 that are actually
      "sets" and not just "random picture dumps".

Leaving open so others can see why the cap is set & that the cap is not
going to be increased.

—
Reply to this email directly or view it on GitHub
#17 (comment).