create-introducer ~/.tahoe/introducer
$ tahoe start -d ~/.tahoe-client
$ tahoe start --node-directory=/home/user/.tahoe/introducer
(Some commands support appending the node directory. All commands IIRC
support -d, --node-directory= )
str4d
On 11/12/2013 09:24 PM, Ed Kapitein wrote:
On Tue, 2013
tickets on the Tahoe-LAFS bug tracker about both
the multi-introducer system, and a no-introducers system. One (or
both) of these should eventually get merged into Tahoe-LAFS.
str4d
On 03/11/2014 02:28 PM, Zancas Dearana wrote:
On Sun, Mar 9, 2014 at 7:59 PM, xiao_s_yuan xiao_s_y...@163.com
wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey Zooko and David,
I was busy over the past several weeks, but my timetable has settled
down. And yep, DST has altered my availability. I am generally
available from 21:00 UTC most days, but can meet at 20:00 UTC if that
is better.
str4d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Natanael wrote:
Den 17 feb 2015 07:56 skrev str4d st...@i2pmail.org:
Other than that, there is no difference. Non-honest Tahoe-LAFS
nodes are perfectly capable of joining a standard Tahoe-LAFS
network and sending fake replies. So any Sybil
of the grid's multiple introducers
for years, so nearly all existing grid nodes use it. I have created a
fork of 1.11.0 that rewrites old-style FURLs in announcements to
new-style, and vice versa:
https://github.com/str4d/tahoe-lafs/tree/i2p-grid-migration
I am running this build at my introducer