[tahoe-dev] Tahoe-LAFS is widely misunderstood

[Greg Troxel]

  This is the latest example in a string of events which has convinced
  me that we have a serious problem with our documentation and
  communication (or "marketing"). We are failing to make the basic
  properties clear to a large class of readers. Below I list some other
  misunderstandings I've noticed.

  This is bothers me, because I've long thought (probably inspired by
  something that Brian once said) that even if Tahoe-LAFS fails as a
  working implementation then it will still have been worth it if people
  learn from it about what is possible. To maximize this value we have
  to communicate clearly about what properties Tahoe-LAFS offers and
  how.

For what it's worth, I discovered tahoe-lafs fairly recently (although I
noticed your release announcements to cryptography@ for a long time but
didn't dig in).   I read the website and the papers and things seemed
clear enough.

It may be that people are assuming things are simpler than they are (in
general, not just about tahoe).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110131/da2c2ff9/attachment.pgp>