Welcome to the world, Tahoe! And congrats to the team on the public release.
I'm curious about application level goals for tahoe. I know that allmydata is in the backup business, but it seems like several design decisions in tahoe are driven by more generic distributed storage constraints (desire for 'alacrity' in download, streaming, etc.), i.e., it seems that tahoe could be used as a generic file-sharing service, which has differnent usage patterns and common case scenarios from backup. Is that an accurate characterization? Care to comment on the tradeoffs/benefits of the design in this regard? I also have some questions about the Verifier, driven mostly by my ignorance I'm sure :) It is clear that it could verify the file from the verifierid, but I think this requires it to download and decode the file, right? Is that sufficient to detect which shares might be corrupt (to assess blame to a specific node), or is there an additional hash for each share that is stored somewhere other than with the share (in the URI, perhaps)? Or some other means to detect corrupt data without reconstructing files remotely? I think this may be of general interest to p2p-hackers so I'm posting here. Very cool stuff. Congrats again. Allmydata should be commended for releasing this openly. Alen On 5/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Dear p2p-hackers: Allmydata, Inc. [1], provider of the "Allmydata" consumer backup product, is pleased to announce the first public release of "Tahoe", a secure, distributed storage grid with a free-software licence. ...
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
