Penguin

Differences between version 19 and predecessor to the previous major change of PerryLorier.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 19 Last edited on Friday, February 20, 2004 10:00:27 pm by ReedLoden Revert
Older page: version 11 Last edited on Sunday, February 23, 2003 3:03:39 am by AristotlePagaltzis Revert
@@ -1,25 +1,23 @@
-''How many EWHATEVER are you going to add, anyway? :) --AristotlePagaltzis''  
-  
 <?plugin WlugMember?> 
-Perry's the guy that put this wiki up.  
  
+Perry's the guy that put this wiki up. He's TheSorcerersApprentice. (Gotta link it somewhere.)  
  
-Perry is the code maintainer for the UnderNet IRC network (rumours that he was giving O-lines for drugs have been greatly exaggerated). 
+Perry is the code maintainer for the UnderNet IRC network (rumours that he was giving O-lines for drugs have been greatly exaggerated). He is also the co-maintainer of UnderNet's CoderCom
  
 He is currently interested in writing a language called Ni (LanguageNi) with JonPurvis. 
  
 JonPurvis, MatthewBrowne and PerryLorier came first in the [ACM] Regional Programming Competitions in 1999ish, went to Orlando in 2000, and after taking numerous pictures of the insides of JonPurvis's pocket, got an HonoraryMention in the World Finals. 
  
-Perry's also the co-maintainer of UnderNet's CoderCom :)  
-  
- Perry wrote a SmallDoorGameSpecification once. 
+Perry wrote a SmallDoorGameSpecification once. And a rant about TabStops. (Link your pages!)  
  
 Perry's gpg-id is 
  pub 1024D/2F33F144 2000-09-23 Perry Lorier (Local network) <perry@coders.tla> 
  Key fingerprint = 0A5F E3C9 8CF7 7FB7 378D 3C1C 7008 11A7 2F33 F144 
  
 Author of WanDaemon, and creator of the MetaNet. 
+  
+Perry looks like this: http://www.feet.net.nz/gallery/raymondhomecoming/raymondshomecoming_042. He also looks like this when he is drunk: http://www.astrolink.org/net/Isomer.jpg (:]). See also RemosisAss.  
  
 Perry's CodingHints. 
  
 Perry's JabberInstantMessaging ID ([JID]) is "isomer@jabber.meta.net.nz" 
@@ -37,12 +35,8 @@
  debian/* http://ftp.nz.debian.org/debian/$1 
  gnu/* http://ftp.gnu.org/gnu/$1 
  foo/*/*/* http://ftp.foo.org/$2/$1/$3 
 ;:The program also keeps a file ~/.grab-hints which has the format "ip lastused cps". ip is the IP address of a server. lastused is the unix time that the server was last used, and cps is the bytes per second transfer rate that we got off that server last time. When selecting which server to d/l from it uses the one with the lowest "cps". The cps value should degrade over time, for instance "cps" every day since lastused, this should be tuneable. if an IP doesn't exist in this file it's cps should be assumed to be "0", so it will be used in preference to any other in the file. This will mean that if you start trying to d/l a whole heap of stuff off "ftp.debian.org" it should try each of the servers in turn, then it will use the fastest one, occasionally retrying the other ones to see if they have improved. Of course if it can't reach a server it should try the next best in the list. If a "MD5SUM" file exists, it should fetch it off one of the *other* mirrors - NOT from the same machine where possible and then verify the file and print a message like "''file'' verified __OK__, or ''file'' __FAILED__ verification. This should be default behavour. The program could also support rate limiting. This program could also distribute hits over the top "n" servers when d/ling. eg: when d/l'ing an [ISO] from say RedHat it could d/l 1mb from ftp.redhat.com, 1mb from ftp.nz.redhat.com, 1mb from another site etc. The first one finished of course d/l's another 1mb chunk. This requires information about which parts of the file have yet arrived. This could very quickly d/l a file. 
-* A [MUD] with a very very smart AI for NPC's. Based on Vampires, with PaulMounsey.  
 * Continue work on UnderNet's [IRC] Server. 
-* Try getting WantedPages working in this wiki.  
 * Add gpg(1)/pgp(1) signing to mailing list software, particularly mailman. All outgoing messages should be signed by the list, or, optionally at the users request, encrypted by the list. Email commands could be ignored if they aren't signed by that user. Incoming messages from users could be verified and rejected if they don't come from a signed key. 
  
 Wanna buy me something? Well, yeah, I doubt you do, but if you really want to, http://www.amazon.com/exec/obidos/registry/201149XSUHH90/ 
-  
-<sneak> and this is what he looks like http://www.feet.net.nz/gallery/raymondhomecoming/raymondshomecoming_042 </sneaky>