Matthew Toseland wrote:
> So it's some sort of micro-trusted-third-parties thing. Hmm. Isn't the
> big worry that people will tend to just re-use their friends' install
> URIs?
>
Installer URIs would be one time use. Friend A could limit Friend B's
use of installer URIs. There is trust that the installer includes the
correct code for Freenet, yes, but it's a mechanism that allows
decentralized distribution even "by" NATted nodes that don't know how or
can't port forward, etc.
> On Mon, Mar 05, 2007 at 05:02:22PM -0600, David Sowder (Zothar) wrote:
>
>> Friend A (wanting to connect with Friend B) does:
>> 1) Gets an installer URI (containing an "access key") from his node's
>> direct (or maybe even indirect mutual friend's) peer (C's)
>> 2) Generates a one-time sharable noderef by asking his own node (A's)
>> via FProxy or FCP
>> 3) Emails the installer URI from step 1 to Friend B (the
>> to-be-peered-with friend), attaching the .fref file generated in step 2
>>
>> Friend B does:
>> 1) Receives the email from Friend A
>> 2) Saves the email attached .fref to disk'
>> 3) Points a web browser at the installer URI from the email
>> 4) Installs a Freenet node using the installer located at the installer URI
>> 5) Double-clicks or otherwise uses the .fref file as configured for
>> Friend B's operating system by the installer to add Friend A's one-time
>> sharable noderef (it contains a code Friend A's node uses to
>> authenticate connection to a peer it didn't previously have a ref for)
>> 6) Trades "normal" noderefs with others to add more peers to his node
>>
>> Friend C does:
>> 1) Gives Friend A permission and access to distribution area of their
>> node to generate installer URIs to be used by Friend B (and Friend A's
>> other friends)
>> 2) Leaves the node up and running enough for Friend B to use the
>> installer URI to install a Freenet node
>>
>> The roles of Friend A and Friend C could be combined in the case where
>> Friend A doesn't have NAT or has proper port forwarding and dyndns, in
>> which case a installer and noderef URI could be used instead. (Provides
>> the installer and connects to the node created by the installer it
>> provided.)
>>
