> > >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. > Anyone whose IP address changes frequently enough for this to be an issue shouldn't be giving their seed.ref file out to anyone in the first place, making the whole argument moot (having said that, I disagree with your argument - but since it is moot, I can't be arsed to debate it).
>>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. > Actually it would make more sense to provide an interface to this through fproxy, but expediency before a release is no basis upon which to make design decisions. Ian. _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
