plowup(1)

πŸ“¦
version 2.1.7 Β· 2 versions
, in nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

✨ NAME ✨

plowup(1) β€” simple upload manager for file sharing websites. This one is from Plowshare for Bash 4, bestie, and it is literally here to make uploads less cursed. πŸ’–

🌸 SYNOPSIS 🌸

plowup [OPTIONS]...  [MODULE_OPTIONS]...  MODULE URL|FILE[:DESTNAME]...

πŸ¦‹ DESCRIPTION πŸ¦‹

plowup is a command-line tool designed for automatic upload on file-sharing websites. It acts like a web browser, retrieving pages and filling HTML forms. Iconic behavior, no cap. ✨

Anonymous upload is not allowed by all sites β€” some of them may require authentication. See specific module options below. πŸ‘‘

🌈 OPTIONS 🌈

🧑 Common options 🧑

  • -i, --interface=IFACE β€” If your machine has several network interfaces, force using the IFACE interface. Pick your network lane, bestie. πŸ›£οΈ
  • -r, --max-retries=N β€” Set maximum retries for upload failures. Apply on module exit value: 1 (fatal error), 3 (network error), 7 (captcha error). Default option value is 0 (no retry) and applies for one single upload. πŸ’…
  • -t, --timeout=SECS β€” Cancel upload download after SECS seconds of waits. Apply on module exit value: 10 (temporary unavailable error). This error mainly occurs on remote upload operations. Default option value is disabled (no timeout, infinite) and applies for one single upload. ⏳
  • --cache=METHOD β€” Cache policy regarding module storage space. Each module is able to save data (credentials, authentication session, or tokens) in order to be reused later. Available values:
    • none β€” module storage file is deleted before each item processing. Temporary directory is used.
    • session (default) β€” module storage file is deleted at the end of plowup execution. Temporary directory is used.
    • shared β€” module storage file is global and located (in ~/.config/plowshare/storage/). It can be accessed by any other instance of plow* scripts.
⚠️ Warning: There is no atomicity (or file locking) on concurrent access. Be so fr.
  • Example: Multiple file upload using a premium account. If supported by module, login stage could be performed once. πŸŽ€

πŸ•΅οΈ Captcha options πŸ•΅οΈ

  • --9kweu=KEY β€” Use 9kw.eu service to solve captchas. πŸ”‘
  • --antigate=KEY β€” Use Antigate.com service to solve captchas. πŸ”‘
  • --captchabhood=USER:PASSWORD β€” Use Captcha Brotherhood service to solve captchas. πŸ‘―
  • --captchacoin=KEY β€” Use CaptchaCoin service to solve captchas. πŸͺ™
  • --deathbycaptcha=USER:PASSWORD β€” Use Death by Captcha service to solve captchas. πŸ’€
  • --captchamethod=METHOD β€” Force specific captcha solving method (if unspecified it is autodetected). Available values:
    • imgur β€” upload image to Imgur.com service, print image url in console and prompt for manual entering. Useful for NAS and embedded devices.
    • none β€” abort if captcha solving is requested (even if automatic solving service is available).
    • online β€” use captcha solving website only (9kweu, Antigate, CaptchaBrotherhood, CaptchaCoin or DeathByCaptcha account required).
    • fb β€” display image in framebuffer console and prompt for manual entering. Looks for framebuffer viewers: fbi, fim. FRAMEBUFFER environment variable can contain device file. Default is /dev/fb0.
    • nox β€” display image in console (text) and prompt for manual entering. Looks for ascii viewers: img2txt, aview, tiv.
    • x11 β€” display image in an X11 window and prompt for manual entering. Looks for viewers: display, feh, sxiv, qiv. DISPLAY environment variable must not be empty. πŸ–ΌοΈ
  • --captchaprogram=PROGRAM β€” Call external program or script for solving captchas. Provided executable can be located in PATH environment variable. Three arguments are given:
    • $1 module name (lowercase). For example: mediafire.
    • $2 image filename (with full path).
    • $3 hint or captcha type (string). For example: recaptcha, solvemedia or digits-4.

Return value (on stdout) and exit status:

  • 0 β€” solving success. Captcha Word(s) must be echo'ed.
  • 2 β€” external solver is not able to solve requested captcha. Let plowup continue solving it normally (will consider --captchamethod if specified).
  • 7 β€” external solver failed. Note: this exit code is eligible with retry policy (-r/--max-retries).

Note: plowup legacy exit errors can also be returned, for example: 1 (fatal) or 3 (network). 🧠

🎚️ Tuning settings 🎚️

  • --max-rate=SPEED β€” Limit upload maximum speed in bytes per second. Suffixes are:
    • k for kilobytes (kB i.e. 1000),
    • M for megabytes (MB i.e. 1000^2),
    • K or Ki for kibibytes (KB or KiB i.e. 1024),
    • m or Mi for mebibytes (mB or MiB i.e. 1024^2). πŸš€
  • --min-rate=SPEED β€” Limit upload minimum speed in bytes per second (for a delay of 30 seconds). Suffixes are the same than --max-rate. 🐒
  • --temp-directory=DIRECTORY β€” Directory for temporary files: cookies, images, ... πŸ—‚οΈ
  • --name=FORMAT β€” Format destination filename (applies on each file argument). Can be useful if you want to append or prepend a string to all your files. Default format string is "%f". Interpreted sequences are:
    • %% β€” raw % character
    • %f β€” destination (remote) filename
    • %g β€” destination (remote) filename (without extension)
    • %G β€” destination (remote) filename (without extension, greedy)
    • %h β€” MD5 hash (32-digit hexadecimal number, lowercase letters)
    • %l β€” source (local) filename
    • %m β€” module name
    • %s β€” file size (in bytes)
    • %x β€” extension (without dot character) of %f (not greedy) ✨
  • --run-before=PROGRAM β€” Call external program or script before upload file processing. Provided executable can be located in PATH environment variable. Messages can be sent to stderr, stdout is trashed. Three arguments are given:
    • $1 module name (lowercase). For example: mediafire.
    • $2 local filename
    • $3 destination filename
    • $4 cookie (initially empty) file given to upload module function.

Exit status:

  • 0 β€” script success. plowup continue normally.
  • 2 β€” script explicitly requests skipping current file.

Note: Any other script exit status like 1 (fatal) or 3 (network) will be ignored (an error message will be reported). 🫢

  • --printf=FORMAT β€” Print results (on stdout) in a given format (for each successful upload). Default format string is "%L%M%u%n". Interpreted sequences are:
    • %% β€” raw % character
    • %a β€” admin url or admin code (rare case)
    • %A β€” same as %a but url is escaped for JSON usage
    • %M β€” empty if %a is empty, or alias to "#ADM %a%n".
    • %d β€” delete url
    • %D β€” same as %d but url is escaped for JSON usage
    • %L β€” empty if %d is empty, or alias to "#DEL %d%n".
    • %f β€” destination (remote) filename
    • %l β€” source (local) filename
    • %m β€” module name
    • %n β€” newline
    • %s β€” filesize (positive integer in bytes)
    • %t β€” tabulation character
    • %T β€” 24-hour clock time of finished file upload. 8 characters string in the format "HH:MM:SS" (invoke /bin/date +%T).
    • %u β€” download url
    • %U β€” same as %u but url is escaped for JSON usage 🎯

πŸ“ Logging options πŸ“

  • -v, --verbose=LEVEL β€” Set output verbosity level:
    • 0 β€” none,
    • 1 β€” errors,
    • 2 β€” notice (default behavior),
    • 3 β€” debug,
    • 4 β€” report (very noisy, log HTML pages). πŸ”Š
  • -q, --quiet β€” Alias for -v0. Do not print any debug messages. 🀫

πŸŽ€ Miscellaneous options πŸŽ€

  • --no-color β€” Disables log messages (stderr only) output coloring. 🎨
  • --no-curlrc β€” Do not use curl config file (~/.curlrc). 🚫
  • --curlrc=FILE β€” Force using an alternate curl configuration file. Replaces ~/.curlrc if it exists. This option has no effect when --no-curlrc is defined. πŸ“„
  • --no-plowsharerc β€” Do not consider any configuration file. 🚫
  • --plowsharerc=FILE β€” Force using an alternate configuration file (instead of per-user or systemwide plowshare.conf). This option has no effect when --no-plowsharerc is defined. πŸ“„
  • --modules β€” Display all supported module names (one per line) and exit. Useful for wrappers. 🧩

πŸ’ Generic program information πŸ’

  • -h, --help β€” Display main help and exit. πŸ†˜
  • -H, --longhelp β€” Display complete help (with module options) and exit. πŸ†˜
  • --version β€” Output version information and exit. 🏷️

πŸ‘‘ MODULE OPTIONS πŸ‘‘

πŸ’– Common options πŸ’–

  • -a, --auth=USER:PASSWORD β€” Use premium account. πŸ’Ž
  • -b, --auth-free=USER:PASSWORD β€” Use free account. πŸ†“
  • -d, --description=DESCRIPTION β€” Set file description. πŸ“
  • --folder=FOLDER β€” Folder to upload files into. Usually a (leaf) folder name (no hierarchy assumed). πŸ“
  • -p, --link-password=PASSWORD β€” Protect your files with a password. May require premium account. πŸ”’
  • --email-from=EMAIL β€” <From> field for notification email. πŸ“§
  • --email-to=EMAIL β€” <To> field for notification email. πŸ“§

πŸ› οΈ Advanced options πŸ› οΈ

  • --async β€” Asynchronous remote upload (only start upload, don't wait for link). ⚑
  • --private β€” Do not allow others to download the file. πŸ™ˆ

All switches are not implemented nor required for all modules. See long help message for detailed modules option list. πŸ’…

πŸ“‚ FILES πŸ“‚

  • /etc/plowshare.conf β€” Systemwide configuration file. 🏒
  • ~/.config/plowshare/plowshare.conf β€” This is the per-user configuration file. 🏠

The file format is described in plowshare.conf(5). πŸ“–

  • ~/.config/plowshare/exec/ β€” Additional directory considered when searching for executable. See --captchaprogram switch. 🧚
  • ~/.config/plowshare/modules.d/ β€” User directory considered when searching for modules at startup (plowup will try to open ~/.config/plowshare/modules.d/*/config). One file per module (hoster). 🧩
  • ~/.config/plowshare/storage/ β€” Directory used for storing data (one file per module) among sessions. See --cache=shared switch. πŸ’Ύ

🌸 ENVIRONMENT VARIABLES 🌸

Okay bestie, these little env vars can lowkey change how plowup behaves β€” iykyk:

  • DISPLAY β€” the X11 display server address, and it's what gets used to actually show captchas on screen. Peep the --captchamethod=x11 docs down below πŸ’…
  • FRAMEBUFFER β€” this one's for showing captchas too. See the --captchamethod=fb documentation πŸ’–
  • HOME β€” plowup goes looking for your user config directory in ~/.config/plowshare (check the FILES section above πŸ‘†). If it finds it, then ~/.curlrc gets used too β€” unless you hit it with --no-curlrc to disable that ✨
  • PLOWSHARE_CURL β€” lets you point at a totally different curl command (a $PATH search is considered, no cap). If you don't set it, plain old curl is used πŸ¦‹
  • PLOWSHARE_JS β€” same energy but for the js command β€” specify an alternate one (again, $PATH search is considered). Not defined? Then js is what runs πŸŽ€
  • XDG_CONFIG_HOME β€” the directory where your user configuration files live. If it's not set, ~/.config is assumed, periodt 🌸

πŸ’€ EXIT CODES πŸ’€

So when plowup bails, it tells you why with these numbers. Here's the whole mood ring:

  • 0 β€” Success! We ate. πŸ”₯
  • 1 β€” Fatal error. Either the upstream site updated on us or something unexpected happened 😭
  • 2 β€” No available module (the module name you gave literally does not exist) πŸ™ˆ
  • 3 β€” Network error. Mostly curl-related stuff 🫢
  • 4 β€” Authentication failed (bad login or password, bestie) πŸ’”
  • 5 β€” Timeout reached (go look at the -t/--timeout command-line option) ⏳
  • 6 β€” Maximum tries reached (refer to the -r/--max-retries command-line option) πŸ”
  • 7 β€” Captcha generic error 🧩
  • 8 β€” System generic error πŸ’»
  • 10 β€” That feature (the upload service) seems temporarily unavailable from upstream β€” your user account may be temporarily banned πŸ‘€
  • 12 β€” Authentication required (for example: anonymous users can't do remote upload) πŸ”
  • 14 β€” Can't upload a file that's too big (either it's a hoster limitation or you need more permissions) 🐘
  • 15 β€” Unknown command line parameter or incompatible options 🚫
  • 16 β€” Asynchronous remote upload started (so we can't predict the final status, sorry bestie) πŸŒ€
Lowkey important: if plowup is invoked with multiple files and one or several errors occur, the first error code gets returned added with 100. So like, don't panic when you see a 103 or whatever πŸ’€

πŸ‘‘ AUTHORS πŸ‘‘

Plowshare was initially written by Arnau Sanchez. Check out the AUTHORS file for a list of some of the many other contributors β€” there are a lot of them and they're all icons fr fr 🫢

Plowshare is (C) 2010-2016 The Plowshare Team 🌈


πŸ¦‹ SEE ALSO πŸ¦‹

Go read these too, they're the whole friend group:

plowdown(1), plowdel(1), plowlist(1), plowprobe(1), plowshare.conf(5), plowmod(1).


And that's the whole page, bestie!! πŸŽ€ This one's from the GPL corner of the world, dated July 13, 2016, and it's the plowup(1) manpage β€” go forth and upload slayfully πŸ’…βœ¨

πŸ“¦ where this page comes from