Anypaste

Anypaste is a file sharing site aggregator for *nix-like systems (Mac, Linux, BSD, etc). It uses the mime type of a file to automatically detect compatible hosting sites. For example, if you run anypaste something.jpg, it will get uploaded to tinyimg.io, an image hosting site. If you run anypaste something.m4v, it will get uploaded to SendVid, a video hosting site. More information about Anypaste can be found on the official website: anypaste.xyz.

Demo

Install

Anypaste is just a shell script. It's hosted at https://anypaste.xyz/sh. A quick command to install it is: sudo curl -Lo /usr/bin/anypaste https://anypaste.xyz/sh && sudo chmod +x /usr/bin/anypaste.

Basic Usage Examples

• anypaste file.jpg: Upload file.jpg, automatically selecting the plugin (standard usage).
• anypaste file.jpg file.m4v: Upload multiple files, with automatic plugin selection for both.
• anypaste -p gfycat file.m4v: Upload file.m4v; use a plugin containing gfycat in its name (manual plugin selection).
• anypaste -l: List all plugins/sites.
• anypaste -l file.m4v: List all plugins/sites compatible with file.m4v.
• anypaste -t private launch-codes.txt: Upload launch-codes.txt to a "private" site (URLs are not publicly listed).
• anypaste -f -p gfycat something.tar.gz: Upload something.tar.gz with gfycat, even though gfycat is not compatible (override compatibility checks).
• anypaste some-directory: Upload some-directory, a compressed tarball will automatically be created (.tar.gz)

Website

Documentation can be found on the Anypaste website, as well as the complete list of plugins. The website is open source and can be contributed to in its GitHub repo.

Contributing

Please, make some plugins so we can support more sites! If the plugins seem good enough, I may even make them built-in plugins! Additionally, PRs to improve "Anypaste Core" are also welcome.

Running Tests

On the master branch, all the test*.sh files should execeute without error and all shell files should pass shellcheck (including the tests). The test-plugins.sh and test-integration.sh tests perform actual network requests, so are somewhat finnicky, and are not tested automatically in Github actions. It may be useful to run only certain tests at a time, eg ./test-plugins.sh -- test_gofile. Some of the plugin tests actually download the file from the direct link and ensure it's the same as the original, but this isn't possible for all plugins, so test-plugins.sh is no guarantee that the plugin is working as expected.