Someone should do a dropbox replacement using tahoe lafs.

I've been following Tahoe-LAFS for some time now, and IMHO it is not suited for the thing I wanted to use it for. If people go off-line for some reason and the node doesn't say that to the introducer (e.g. network split, someone pulls his network cable, wifi?) the whole grid will become unresponsive due to the fact that clients try to contact that node. This is especially the case for small grids, on larger grids, this might not be such a big problem. But I haven't tested the latter. A people posted about this on the mailing list last few weeks.

Yes, I'm using it almost year very intensively (for backups ~50GB). I even made binding for pyfilesystem https://code.google.com/p/pyfilesystem so anybody can mount Tahoe-LAFS as normal drive (Windows, Linux, Mac).

Unfortunately there is no real effort for accounting, I think joining Tahoe and Bitcoin would be great. Unfortunately everybody who says that running Tahoe-LAFS is too much complicated is right. There is effort to simplify installation on all platforms, but IMHO it is not ready for end user yet. On the other side, TahoeLAFS is great piece of software!

Question to stability - there were made massive improvements and I can say it is pretty stable now. But I don't know which type of connection uses peers in my grid.

It said I have zero peers after I wrote the stuff for my introducer node or whatever.

What didn't work when you built it without MingW? MingW really should be optional and if it was required for you then I'd like to know why. It probably means there is a 3rd party library that for some reason isn't hosted here:

http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html

But I really need to know which library was missing or which other error was encountered in order to fix it.


Could you please update the wiki page to fix it so the next person won't hit these two issues?

I figured out how to use it, with some difficulty and some heart jumping moment.(Do not post URI to private data)

http://bt.irlbtc.com/view/2236.0

For those who want bitcoin/tahoe-lafs integration, pledge your bitcoin where your mouth is.

We Tahoe-LAFS hackers are actively working on "accounting", which means enabling storage servers and storage clients to discriminate among one another and to track which ones are used for how much storage. There is extensive technical detail available, although some of it may be for an earlier design than the current effort:

http://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~accounting&order=priority

http://tahoe-lafs.org/trac/tahoe-lafs/wiki/QuotaManagement

http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AccountingDesign

http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/proposed/accounting-overview.txt

A digital payment scheme such a BitCoin would probably fit into Tahoe-LAFS pretty easily once we have accounting.

Nobody has written it down in great detail, but several of the Tahoe-LAFS developers have a lot of ideas about it. There is significant interest, for example Brian Warner—who is currently the leader in "most lines of code in the current version of Tahoe-LAFS"—went so far as to reimplement some BC functionality in Python a couple of months ago.

The basic idea is merely that a storage server agrees to store and serve your data only if pay it. There are a large number of details that would need to be worked out beyond that basic idea of course. I currently think a long-term relationship would probably work better than a per-transaction micropayment, so for example you could deliver a payment to each of your storage servers once per month in return for continued service.


Tahoe-LAFS is great at what it is designed for—reliable (secure) distributed storage. If that's what you want, then I encourage you to use or extend Tahoe-LAFS. If you want a substantially different sort of behavior then I would like to learn more about your use case.

Pshaw, 2008 is nothing—we have open tickets from 2007!

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/20

You can see recent activity by looking at the trac timeline or the tahoe-dev mailing list, or the tahoe-lafs-weekly-news mailing list.

Regards,

Zooko