VRipper!

This is my spin for a cross-platform gallery ripper for vipergirls.to

GitHub Image

Donation

To support this project, you can make a donation to its current maintainer

"Buy Me A Coffee"

Or with Cryptocurrency

ETH: 0xDdac82B16dC5E3D742fc915ffF583D8548A301cA

BTC: bc1qcqudnkrndwyadsjwrxww42svkf8trnzx3c8vlr

Supported Image Hosts

The following hosts are supported:

Installing VRipper

Windows macOS (Intel) macOS (Apple silicon) Linux Java
Installer (EXE)
Installer (MSI)
Portable (ZIP)
Installer (DMG)
Installer (PKG)
Portable (ZIP)
Installer (DMG)
Installer (PKG)
Portable (ZIP)
Linux (amd64) (DEB)
Linux (x86_64) (RPM)
Portable (ZIP)
Java GUI (noarch)
Java Web (noarch)

Source code and previous versions are available on the Releases page.

Application data (application logs, settings and persisted data) is stored in:

Docker Support

The project is supplied as a container image and can be run locally or in production using Docker. By default:

Run with docker run

docker run -d \
  -p 30000:30000 \
  -p 8080:8080 \
  -e GRPC_ENABLED=true \
  -e GRPC_PASSPHRASE=my-secure-secret \
  ghcr.io/dev-claw/vripper-web:latest

Run with Docker Compose

services:
  app:
    image: ghcr.io/dev-claw/vripper-web:latest
    environment:
      - GRPC_ENABLED=true
      - GRPC_PASSPHRASE=super-secret-passphrase
    ports:
      - "30000:30000"
      - "8080:8080"

Tip: For production, prefer storing the passphrase as a secret (see Security Notes below) rather than writing it directly in the Compose file.

Environment Variables

The container supports these environment variables for enabling and securing the gRPC server.

GRPC_ENABLED

export GRPC_ENABLED=true
environment:
  - GRPC_ENABLED=true

GRPC_PASSPHRASE

export GRPC_PASSPHRASE="my-very-strong-passphrase"

Default Ports

You can map these ports when running the container. The application supports overriding these defaults with environment variables (GRPC_PORT, SERVER_PORT), configure them as needed.

Important Note About Proxies

The use of proxies within VRipper is worthless, please stop using them for now. You will get 403 error codes.

403 is a response code coming from Cloudflare to block VRipper from accessing the site, Cloudflare is doing the job it is supposed to do, which is blocking automated requests from accessing the site.

If your ISP is blocking access to vipergirls.to domain, consider using a VPN or Cloudflare WARP to bypass the block.

Feed API

VRipper uses the ViperGirls feed API v2 (vr.php) through the viper.click domain. The feed endpoint can be overridden with the VRIPPER_FEED_URL environment variable or the -Dvripper.feed.url system property.

The v2 API provides thread and post metadata (author, post date, edit date, starter, reply/view counts, latest post information), gzip compression and ETag caching.

Thread Library and Subscriptions

Thread Library holds multi-post threads added from links. If a link resolves to a single post, or to a thread at or below the configured auto-queue threshold, it is queued directly for download. Larger threads stay in the Thread Library so the user can choose which posts to grab.

Subscriptions is a separate, authentication-only list of the user's ViperGirls subscriptions. It is never merged into the Thread Library. Subscribed threads can still be opened to grab individual posts.

Incremental refresh

Thread Library refreshes use the persisted newest_postid with the API's since parameter, so only posts newer than the last known post are fetched. since does not catch posts approved later by a moderator or images added to old posts; a full refresh now and then catches those, and ETag makes it cheap. dedupe=1 only deduplicates within one response, so VRipper keeps its own downloaded-post list across runs.

All thread requests are paged: VRipper always sends limit=500 and follows pager.next_after with since until pager.more is 0. Pages are combined before metadata, auto-queue decisions, and post selection are evaluated, so large threads no longer depend on a single oversized response. Image deduplication is applied across the collected pages, not only within one API response.

The watcher refreshes subscription metadata when a ViperGirls account is configured, and refreshes Thread Library metadata without authentication. It is refresh-only: it does not queue posts automatically. It uses the configured interval (5-1440 minutes), applies jitter and exponential backoff on failures, prevents overlapping refreshes, and persists its last run/result in watcher-state.json under the VRipper application data directory.

Instructions to run from Jar file

You need Java 21+, you can download from https://adoptium.net/

Download the latest jar file from the Release page, open a command prompt and run the jar file using the following command

For the GUI app

javaw -jar vripper-gui.jar

For the WEB app

java -jar vripper-web.jar

Application data (application logs, settings and persisted data) is stored in the location where you launched the jar for both GUI and WEB

How to build

You need JDK 21 and a recent version of maven 3.8.x+

To build, run the following command:

mvn clean install

Build artifact is located under

vripper-project\vripper-gui\target\vripper-gui-{{version}}-jar-with-dependencies.jar

Copy the artifact into any other folder and run:

java -jar vripper-gui-{{version}}-jar-with-dependencies.jar