Show HN: I am building Reesd, a redundant storage service

I really wish that more services that dealt with documents just exported either a synthetic WebDAV or SSH server.

Mounting either of those server-types as a directory is simple and straightforward on Windows, OSX, or Linux, which is something that can't be said for pretty much anything else.

I really wonder why S3 isn't (mainly) a WebDAV service, for that matter...

The bare idea is very much similar to S3, i.e. a file store. I hope to bring a different value with things like webhooks, Docker images rebuilt automatically as files are uploaded (e.g. for reconfiguration prior to deployment on a cluster of machines), ... agreed these additional features are vaporware but I get started :)

Now, I really think that re-using scp is neat. For instance if you have tools to manage a cluster of machines, it is entirely possible you are already using SSH deploy keys (i.e. you have tools to manage SSH-based credentials). But sure you are probably also using other services that requires API keys.

That would be similar. Indeed the redundant backend can be implemented in various ways. Now I would really like to experiment with Bup to provide historization in addition to deduplication (again this could be implemented with some underlying file systems, but I really like Git/Bup).

The beauty of Tarsnap is to provide a tar-like command-line tool. Here, while the later goal is to provide storage in a more generally accessible way, the beauty is to use scp as-is, which you already have (if you're a developer).

A client-side encryption tool could be implemented and use any scp accessible hosts, but that would not be really a Tarsnap equivalent: there is still the problem of avoiding redundant storage and traffic. Bup could be a solution here.

I think the main difference is that tarsnap is a backup tool while reesd is a multi-purpose tool.