3 ms·

Thanks for the recc. Just spent some time reading the Tarsnap website. It sounds to be a very competitive solution, both in terms of operational transparency (d

by d_r 16y ago

Thanks for the recc. Just spent some time reading the Tarsnap website. It sounds to be a very competitive solution, both in terms of operational transparency (detailed, no-gimmick website) and the layer of security. Hope it's not a stupid question, but how do you deal with the "bus factor" (a.k.a. "truck factor")? In other words, if the service relies on encrypted S3 backups and the founder exits for whatever reason, is there a contingency plan? (http://en.wikipedia.org/wiki/Bus_factor http://en.wikipedia.org/wiki/Bus_factor)

cperciva 16y ago
how do you deal with the "bus factor"? I don't. If I get hit by a bus, Tarsnap will almost certainly cease to exist. That said, the service runs itself quite happily on its own (I've gone for months without touching any "live" code) so the odds are very good that Tarsnap users would have plenty of time to download their data between "email goes out announcing bus hit and account balances get refunded" and "service shuts down". I intend to solve the bus-factor issue once Tarsnap gets larger, but right now it's not financially feasible to bring someone else in.