A brief description of Tahoe
From http://www.tahoe-lafs.org:
Tahoe-LAFS is a Free and Open cloud storage system. It distributes your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire filesystem continues to function correctly, including preservation of your privacy and security.
Tahoe on I2P
There are two competing implementations of Tahoe-LAFS that are available for I2P:
- Duck's method which goes through the eeProxy
- Socrates' method which communicates via BOB
Duck's implementation using the HTTP Proxy
KillYourTV 'hijacked' the Tahoe-LAFS installer after Duck went missing. It was last updated in June 2014 for the 1.10 release. Tahoe-LAFS works in Windows and you don't have to compile anything yourself.
On this site you can find installation and configuration instructions as well as various scripts and other utilities for use with Tahoe on I2P.
If you've already installed Tahoe, this list of example URLs can be used to confirm your Tahoe installation is working properly.
A small TODO/Progress list and changelog are also available.
We could use more FAQs (and perhaps an I2P-specific bug tracker?).
i2py-tahoe, using BOB & Seedless
i2py-tahoe is Socrates' fork, based on a darcs snapshot, and was last updated in July 2011. It is available at str4d's git repo hosting service. Be advised that i2py-tahoe is vulnerable to a security bug fixed upstream with the release of v1.8.3.
All known documentation about i2py-tahoe can be found on its page.
Which one should I use?
"You need to decide for yourself which suits your needs best."
Most people are using Duck's implementation--and it has no known security issues--so that might be the best option. Upstream tahoe is also interested in making Duck's patches part of the official Tahoe-LAFS distribution. i2py-tahoe also has broken MDMF patches applied (search the tahoe bugtracker for regressions introduced with 1.9).
Duck's implementation is the better option for me. It may not be the best option for you.