Anything on this list that you can verify is up, or have other reason should not be removed, please comment below. 1.fcp.freenet.i2p 2.fcp.freenet.i2p 55cancri.i2p adab.i2p always.i2p amazone.i2p amiga.i2p amobius.i2p anonymnet.i2p anonynanny.i2p antipiracyagency.i2p antipiratbyran.i2p archive.i2p archive.syndie.i2p ardvark.i2p arkan.i2p asciiwhite.i2p aspnet.i2p asylum.i2p aum.i2p awup.i2p bacardi.i2p badfish.i2p badtoyz.i2p bash.i2p bdl.i2p bdsm.i2p betaguru.i2p beyond.i2p b.i2p...

As long as it's clearly indicated how the changes work, I don't see a problem :) Link Post   Topic   (x) Tue, 23 Feb 2010, 11:31pm #3 MOSFET I2P Regular Once upon a time it was thought that hosts.txt entries were local, ie. I might have dest A with name B.i2p while you have dest A with name C.i2p. The addressbook supports that idea with privatehosts.txt. (There were some rather ill-defined ideas about 'pet names' and how the addressbook might evolve that aren't important now.)

As long as it's clearly indicated how the changes work, I don't see a problem :) Post   Topic   (x) Tue, 23 Feb 2010, 11:31pm #3 MOSFET I2P Regular Once upon a time it was thought that hosts.txt entries were local, ie. I might have dest A with name B.i2p while you have dest A with name C.i2p. The addressbook supports that idea with privatehosts.txt. (There were some rather ill-defined ideas about 'pet names' and how the addressbook might evolve that aren't important now.)