fixed some URLs, and the irc proxy is loaded on startup

readme.txt

-$Id: readme.txt,v 1.1.1.1 2004/04/07 23:41:54 jrandom Exp $
+$Id: readme.txt,v 1.2 2004/06/09 09:27:51 duck Exp $
 I2P Router 0.3
 
 You have installed a development release of I2P - a variable latency secure 
@@ -33,9 +33,11 @@ console).  At that point, you can use any of the various proxies:
   tunnel any HTTP requests that don't point at an eepsite (e.g. http://i2p.net/)
   through I2P to an outbound squid proxy - with this, you can browse the web
   anonymously.
-* startIrcProxy: starts an anonymous tunnel to an anonymously hosted IRC server
-  (irc.duck.i2p) - use your favorite irc client and connect to localhost:6668 
-  and join us on #i2p
+* ircProxy: this proxy is also started automatically 2 minutes after the router
+  is started, listening on port 6668.  If you fire up your favorite irc client
+  to irc://localhost:6668/#i2p you'll be logged on to irc.duck.i2p, an 
+  anonymously hosted IRC server (which is hooked up to the IIP server and has
+  bridges to a few channels on irc.freenode.net)
 
 === Problems accessing eepsites or servers
 
@@ -47,7 +49,7 @@ you have TCP connections.  If you don't have any, make sure your firewall / NAT
 allows inbound access to your I2P port (which you specified during 
 installation).  If thats fine, but you only see one routerInfo-*.dat file 
 underneath your netDb/ directory, run the reseed script to pull some new peer 
-references (it contacts http://i2p.net/i2pdb/ and downloads those files.  
+references (it contacts http://dev.i2p.net/i2pdb/ and downloads those files.  
 alternately, you can get routerInfo files from any of your friends, etc)
 
 If you still have problems, get in touch with the I2P team (contact info below)
@@ -57,19 +59,19 @@ If you still have problems, get in touch with the I2P team (contact info below)
 Our website can be found at http://www.i2p.net/
 The development and user community hangs out on a few different linked irc
 chats - IIP's #i2p, freenode.net's #i2p, and the in-I2P irc network's #i2p
-(both irc.baffled.i2p and irc.duck.i2p).  All of those channels are hooked
-together, so join whichever one meets your needs.
+(the irc.duck.i2p server).  All of those channels are hooked together, so 
+join whichever one meets your needs.
 
 There is also a relatively low traffic mailing list:
-http://i2p.net/mailman/listinfo/i2p with archives at
-http://i2p.net/pipermail/i2p/
+http://dev.i2p.net/mailman/listinfo/i2p with archives at
+http://dev.i2p.net/pipermail/i2p/
 
 The source can be retrieved from http://i2p.net/i2p/ as well as the latest 
 binary distributions.
 
 You can pull the latest code via cvs:
-cvs -d :pserver:anoncvs@i2p.net:/cvsroot login
-cvs -d :pserver:anoncvs@i2p.net:/cvsroot co i2p
+cvs -d :pserver:anoncvs@cvs.i2p.net:/cvsroot login
+cvs -d :pserver:anoncvs@cvs.i2p.net:/cvsroot co i2p
 The password is "anoncvs".  
 
 === Acknowledgements
@@ -82,6 +84,6 @@ http://www.i2p.net/team
 === Licenses
 
 All code included here is released under an open source license.  To review
-the I2P license policy, please see http://www.i2p.net/node/view/66.
+the I2P license policy, please see http://www.i2p.net/licenses
 If there is any confusion, please see the source code or contact the 
 developers on the i2p list.