/cas/{hashtype}/{hash}/{filename}
a filesystem specification for a generic Content Addressed Storage
the cas filesystem consists of multiple cas directories
/cas
/home/someuser/cas
/tmp/cas
/media/somelabel/cas
/run/media/someuser/somelabel/cas
/mnt/somemointpoint/cas
C:/cas
D:/cas
each of these cas directories has multiple subdirectories, representing different hash types. we call them "hashtype directories"
/cas/md5
/cas/sha1
/cas/btih
/cas/git
/cas/sha256
/cas/size
/cas/todo
exception: size is the file size in bytes
exception: todo is a directory for files with unknown hash, but the hash will be known in the future,
so the files can be moved to other hashtype-directories
- wikipedia: Content-addressable storage
- github.com/milahu/cas_torrent - a bittorrent client with content-addressed storage
- Nix sha256 is bug not feature. solution: a global /cas filesystem - problem: source files and build files are stored in the same CAS format, ... which is a LOSSY transformation, since /nix/store is messing with file permissions. solution: store source files in their original format, to get a LOSSLESS local copy of the source files
- github.com/perkeep/perkeep - Perkeep is your personal storage system for life: a way of storing, syncing, sharing, modelling and backing up content
- github.com/okhosting/awesome-storage
- github topic: content-addressable-storage
- github topic: content-addressed-storage
- Magnet-URI Webseeding libtorrent#7960 - add
casparameter to magnet links