> Freenet URLs should not include the server. The server is a > setting. Setting it in URL will confuse users, and makes as much > sense as having your Web proxy in the URL.
Just to put in my two cents--yes, I think it's important that Freenet URIs _not_ be URLs, that is, not have any location info. Any browser that wants to accept freenet: URIs must either install a small node of its own, connect to a local node, or connect to a remote node by user configuration. It should be more than merely discouraged for hyperlinks to have IPs, it shouldn't be possible. -- Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lcrocker.html> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
