Open Source File Sharing Software

Remote Operation On Files (ROOF) is a FTP client providing: a command line tool as well as an API library, a File system based on FTP protocol named FTPFS (FUSE based) and FTPING tool to check remote FTP server availability.

A simple command line tool, that takes a RSS feed of movie torrents, takes the good quality ones (based on the name) and checks IMDB for their rating. If it is higher than a predefined margin it downloads the torrent.

A CLI to upload files to IPFS and interact with them using wbeb3.storage.

The Fission CLI is now part of the main fission-suite/fission repo. We construct identity, data, and compute solutions for the future of the Internet. Users want data ownership and privacy without compromising on a seamless experience. You want to build a resilient application that is fast, cost-effective, and efficient. We build local-first and edge computing tools that make all of this possible. Fission builds open source protocols and managed solutions that empower developers to construct humane software applications.

This is the far-easiest command line tool for running torrents under Linux. It only has 4 options, but a little-more advanced user can finetune it by editing. Created by Salcay's Boring Hours

This is a continuation of the command line tool createtorrent. While useful, it is lacking in some recent features. The new releases of createtorrent hope to bring createtorrent up to date, making it a modern command-line bittorrent creation program.

a small and simple command line tool which helps to batch download files after applying a filter on filenames or extensions.

Upload static websites to IPFS pinning services and optionally update the DNS. The goal of ipfs-deploy is to make it as easy as possible to deploy a static website to IPFS.

Command line peer-to-peer data transfer tool based on libp2p. There already exists a long list of file transfer tools, so why bother building another one? The problem I had with the existing tools is that they rely on a limited set of servers to orchestrate peer matching and data relaying which poses a centralization concern. Many of the usual centralization vs. decentralization arguments apply here, e.g. the servers are single points of failure, the service operator has the power over whom to serve and whom not, etc. Further, as this recent issue in croc shows, this is a real risk for the sustainable operation of the provided service.