This may appear trivial, but I suspect it is causing serious damage to the network:
The Windows Installer should try to figure out what the node's IP address is automatically, *very few* users will know how to figure out their node's IP address, particularly in Windows - meaning that only a tiny proportion of Windows users will actually be contributing back to the network. By a similar token, the Windows installer should default to setting up a permenant node - not a transient node. The node announcement is delayed so that only nodes which have been up for a while (and which are therefore likely to stay up) will really get insinuated into the network. I suspect that having 99% of Windows users unwittingly set up transient nodes is more damaging to the network than users unwittingly setting up transient nodes when they could be permenant. The Invalid IP Address warning references ARKs, yet I don't see how they will solve the problem of people not setting their IP addresses correctly. The correct way to solve this problem is to allow one node to ask another node what its IP address appears to be externally, so that it can be set without any user intervention. Ian. -- Ian Clarke ian@[freenetproject.org|locut.us|cematics.com] Latest Project http://cematics.com/kanzi Personal Homepage http://locut.us/ -------------- 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/20021116/4abdc85b/attachment.pgp>
