On Tue, 09 Oct 2001, Jason Smith wrote: > Said thelema on Tue, Oct 09, 2001 at 10:31:07AM -0500, > > In the meanwhile, people with dynamic IPs need to either use something > > like dyndns.org so their reference stays up to date or they need to stay > > transient and not share their reference. I guess we should only export > > the reference if they're not transient. > > Quite right. My thoughts are that this no longer applies to the J. > Random Freeneter case. Registering with dyndns might be too much to ask > of the masses. > You're right, at the moment, freenet isn't for the masses.
> I think that what will likely happen is cable/dsl users making a > seed.ref file, and that file being invalid after a few days go by and > their IP changes. That's why I asked about re-generating seed.ref every > time the node starts -- to increase the likelihood that it is valid over > time. > The node only knows what address it is by what you tell it. Regenerating seed.ref files through FCP would require 1) editing the freenet.ini file to tell fred its new address 2) restarting fred and 3) using FCP to get the new seed.ref. Regenerating it when the node starts would require (1) to be done automatically by something, which isn't the right way to do it at all. > Also, with regards to a .5 release, FCP or node-generated seed.ref will > accomplish the same task; but there would need to be an actual > FCP-to-file-on-the-hard-disk implementation ready and bundled with the > .5 software to be of any use. > I agree; if we did put the localnoderef command into FCP, we'd also have to have a command-line interface to it as part of the release. > My final thoughts are that perhaps both should be done, the FCP version > to facilitate future expansion and more elaborate clients. But in any > case, a seed.ref file should definitely be generated at or near install > time with a big glaring, "This is your seed.ref file! Give it to all of > your friends" message, to help with that current problem. > I still don't see why clients would want the noderef. The only programs I can see myself feeding a noderef into are BitchX (to send it over IRC) or mutt (to e-mail it). Thelema -- E-mail: thelema314 at bigfoot.com If you love something, set it free. GPG 1536g/B9C5D1F7 fpr:075A A3F7 F70B 1397 345D A67E 70AA 820B A806 F95D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20011009/eb8f9ecc/attachment.pgp>
