NNCP, from
http://www.nncpgo.org/It's a protocol/tool for async file transfer, built for disconnected/intermittent connectivity amongst known parties (trusted friends as p2p), allowing even for sneakernet-based file transfer.
It's started as a modern take on usenet, but it boggles my mind how cool it is:
Want to send a TV Series to your friend? send it via nncp, and it will make it through either via line-based file transfer (when connection allows, pull or push, cronjob, etc), or even via sneakernet if there is "someone going that way".
Comms priority system lets you hi-prio message-checking via expensive network link vs bulk file transfer using trunk lines later.
It even can be configured to run arbitrary commands on message receive, to allow indexing/processing of files (like a ZFS-receive hook, mail/matrix ingestion...)
See all the usecases: http://www.nncpgo.org/Use-cases.html
As with many of these cool techs, I just wish I had a good reason to use it =D
It's a protocol/tool for async file transfer, built for disconnected/intermittent connectivity amongst known parties (trusted friends as p2p), allowing even for sneakernet-based file transfer.
It's started as a modern take on usenet, but it boggles my mind how cool it is:
Want to send a TV Series to your friend? send it via nncp, and it will make it through either via line-based file transfer (when connection allows, pull or push, cronjob, etc), or even via sneakernet if there is "someone going that way".
Comms priority system lets you hi-prio message-checking via expensive network link vs bulk file transfer using trunk lines later.
It even can be configured to run arbitrary commands on message receive, to allow indexing/processing of files (like a ZFS-receive hook, mail/matrix ingestion...)
See all the usecases: http://www.nncpgo.org/Use-cases.html
As with many of these cool techs, I just wish I had a good reason to use it =D