Don't get me wrong -- I think the p2p style, which foolscap already implements part of -- is sweet. I'd like to improve it, in the interests of making Tahoe-LAFS deployment more automatic for end-users. However, we should probably pay attention to the fact that many of our current users do not use those features, and some of them are actively requesting the ability to turn off those features. Maybe some kind of friendly fork or more targeted packaging would help us manage these diverging deployment scenarios? What needs to be forked? Isn't it just a question of usage, with a mode of client-only, server-only, or both, perhaps enabling reverse connections, and a few other things? All these issues seem trivial in terms of code weight relative to what we have now. _______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE