Store any file on anonymous public services.
Caps uploads files in chunks to anonymous public storage services, such as pastebins, image sharing services, and URL shorteners. Information needed to retrieve the chunks is saved, and can be used with Caps again to reconstruct the original file.
npm install -g caps
usage: caps upload|download|convert [options...] [file]upload options:-b, --chunk-size=262144 maximum chunk size in bytes-v, --vary vary chunk size-r, --redundancy=1 chunk upload redundancy-s, --stores=... comma-separated list of stores to use-x, --exclude=... comma-separated list of stores to excludeconvert options:-i, --input=base64 format of input (see -f)common options:-o, --output=- output to file-f, --format=base64 format of data: json, msgpack, base64, pnggeneral options:-q, --quiet suppress logging-h, --help show help
The default format of Caps retrieval data is a base64 representation of
a msgpacked JSON array, for easy and compact copy-paste. Other formats
are available, and can be selected using the
json: JSON array
msgpack: msgpacked JSON array (binary)
base64: base64 msgpacked JSON array
png: PNG-pixel-data-encoded msgpacked JSON array (binary)
-o option can be used to dump Caps data (or a retrieved file) to a
file. By default data is written to standard output.
Caps splits files into chunks of 256 KiB by default. The (maximum) chunk
size can be set with the
-b option, in bytes. By default each chunk
will be the same size (except the last chunk). The
-v option causes
chunk size to vary based on the maximum chunk size of each store. Each
chunk can be uploaded to multiple stores with the
-r option. This will
provide redundancy in case retrieving a chunk from one store fails.
By default, Caps uploads to any stores capable of storing the specified
chunk size if
-v is not used. The
-s option can be used to set the
list of stores to use. Alternatively, stores can be blacklisted with the
The information needed to retrieve the original file is then written to
standard output, or a file with the
-o option, in the format specified
caps upload -r 2 -f png -o YellowSubmarine.png YellowSubmarine.mp3
Caps reads retrieval data from a file or from standard input. If the
data format is not the default (base64), it must be specified with the
-f option. The file is then downloaded in chunks using the stored
information and reconstructed. The reconstructed file is checked against
the stored SHA checksum, then is written to standard output, or a file
caps download -f png YellowSubmarine.png -o YellowSubmarine.mp3
Caps can convert retrieval data between formats. The input format should
be specified with the
-i option, and the output format with the
caps convert -i png YellowSubmarine.png -f json -o YellowSubmarine.json
Caps is capable of uploading chunks as base64 text (to pastebins or URL shorteners) or as PNG pixel data (to image sharing services). Most services enforce a hard limit on the size of data that can be uploaded, which must be considered when choosing chunk sizes.
|Index||Name||Encoding||Max Chunk Size (bytes)||Notes|
|1||imgur||PNG||999602||Lossless PNGs up to 1 MB|
|5||v.gd||URL||3735||is.gd on a different domain|
|6||pastebin||base64||384000||Nasty rate limits 😞|
File chunks uploaded by Caps are publicly accessible and unencrypted. If you are concerned about privacy, encrypt your files before using Caps.
Storage services may not retain data indefinitely. Do not expect Caps downloads to work forever. For increased chances of successful downloads, use redundancy.
Copyright © 2014, Curtis McEnroe email@example.com
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.