"Scott G. Miller" schrieb: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > We take the server in the URL as a *suggestion*. > > > The priority of who to contact first for the data is as follows: > > > 1. Localhost > > > 2. entries in ~/.freenet > > > 3. entries in /etc/freenet.conf or appropriate master file > > > 4. Suggested server in URL. > > > > > > Fair enough? > > > > Lovely. > > Imagine this: > > Lazy Bob runs a freenet site (like a website). He gets a lot of > complaints from users who haven't configured there browser correctly, and > aren't running a node. These people can't access LazyBob's site. For a > while, LazyBob helps them out getting them connected. But LazyBob is > lazy, and eventually he tires of this. So instead, he starts changing the ???? configure the browser(-plugin) to use localhost:19114 dy default and make a link at the desktop to fserve (or unix-equivalents) when installing the freenet-stuff those who use dial-up-connections have to start a dialer anyway... starting a node is no really big task. bob won't have anything to help -- the page where you can download a freenet-browser(-plugin) should help you getting started > URL's on his site to be freenet://lazybob.com/mykey. he shouldn't do that. there were sugestions to allow only humans to specify an entry-node ... if that is possible with the big browsers > > Then people that link to LazyBob notice this and say "Hey! This is how I > can get people off my back". Bang... freenet dies. > > DO NOT ALLOW SERVERS IN THE URL. as above: only for humans - not for URLs in documents > > Thank you. :) you may wish to enter freenet via a specific node (i've no thougths why you should ;-)
1723 _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
