Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !nntp.giganews.com!nx01.iad01.newshosting.com!newshosting.com!13   
   .81.64.211.MISMATCH!cycny01.gnilink.net!spamkiller.gnilink.net!g   
   ilink.net!trnddc03.POSTED!1b04045d!not-for-mail   
   Newsgroups: alt.os.linux.ubuntu   
   From: Mateus Denigris    
   Subject: Re: Slrn   
   References:        
       
     <87ps84j4o6.fsf@geemail.com>      
   Organization: http://www.teamtuxedo.com   
   X-GnuPG-KeyBlock: http://www.teamtuxedo.com/   
   X-PGP-KeyID: 0xF214D93A   
   User-Agent: slrn/0.9.8.1pl1 (Debian)   
   Lines: 95   
   Message-ID:    
   Date: Wed, 21 Feb 2007 23:12:43 GMT   
   NNTP-Posting-Host: 71.105.178.40   
   X-Complaints-To: abuse@verizon.net   
   X-Trace: trnddc03 1172099563 71.105.178.40 (Wed, 21 Feb 2007 18:12:43 EST)   
   NNTP-Posting-Date: Wed, 21 Feb 2007 18:12:43 EST   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:10849   
      
   -----BEGIN PGP SIGNED MESSAGE-----   
   Hash: SHA1   
      
   On 2007-02-21, Chris Game spake thusly:   
   > On 2007-02-21, Mateus Denigris  wrote:   
   >>   
   >> Your ISP controls your ISP's news server. With Leafnode, you are    
   >> essentially creating your own ISP Newserver. Leafnode will cache    
   >> articles and newsgroups from any source(s) you specify, and your    
   >> news reader then accesses Leafnode as an NNTP server. As far as    
   >> your reader knows, it *is* your ISP's newserver. Leafnode can be    
   >> configured as a cron job that retrieves messages and headers from    
   >> servers at a given time that is convienient for you, without your    
   >> having to do a thing, and it will do so from as many or as few    
   >> servers as you want, and as many or as few messages as you want.    
   >> It is most decidedly _much_ faster than directly accessing the ISP    
   >> NNTP server remotely. Posting is also much more efficient as it is    
   >> done as configured, and messages may be qued as desired.   
   >   
   > Yes, well thanks for the lesson   
      
   any time ;-)   
      
   > , but you didn't explain how the    
   > local server adds functionality to the system   
      
   Sorry about cutting things up so much but I may   
   need to clarify for my own benefit, some definitions   
   here. By local server, I assume you mean having a service   
   running on your own computer rather than remotely. Example:   
   Apache serving pages from your own computer.   
      
   > , particularly in the    
   > caching of headers etc. *which would allow* previously read posts    
   > to be displayed without having to reload them from the NNTP server.   
   > Reading them from another server doesn't count, I can do that from    
   > the ISP's server (if there isn't much traffic it's very fast).   
      
   With Leafnode or SLRNpull, messages are fetched from the ISP NNTP   
   server in bulk and stored on your own computer for as long as you want.   
   This can occur as often as you like. You, not the ISP, decide how you   
   want the messages handled.   
      
   Previously read posts, or any posts for that matter, are there for   
   the taking any time you want. You don't ever have to refetch any   
   messages from the ISP unless you have a really good reason for doing   
   it, or you're just in the mood for it. ;-)   
      
   Having them on your computer as a "local" server also means any news   
   reader can fetch messages from leafnode, which is especially useful   
   for networked computers (like a home lan).   
      
   you can access them as fast as any other file, which is obviously   
   always going to be much, much faster than Downloading them.   
      
   Someone also pointed out that if you are running leafnode to serve your   
   newsgroups to your newsreaders, you have access to them even if your   
   ISP is down for whatever reason.   
      
   And one *really* useful application of SLRNpull is that the message   
   base can be manipulated and searched in any way you want. A wealth   
   of information you don't have to download from the ISP to use. A newsgroup   
   aquaintence wrote a troll hunting application in python that uses the   
   data SLRNpull collects to identify and track trolls, making it really   
   easy to see through their socks. It was *very* fast. I had written a   
   similar python app called headhunter only it had to retrieve the header   
   and body information directly from the ISP. It was painfully slow even on my   
   DSL connection.   
      
   >>   
   >> It's alot of fun being your own ISP. Next class we will discuss    
   >> the joys of SMTP ;-)   
   >   
   > Look forward to it!   
      
   :-)   
      
   Best regards,   
      
   Mateus   
      
   -----BEGIN PGP SIGNATURE-----   
   Version: GnuPG v1.4.3 (GNU/Linux)   
      
   iD8DBQFF3NHglkJ5K/IU2ToRAiCYAJ4xtfTQcC4Fpv8dAAsKk8xYLrofUACZAcHY   
   L+ZuHmi9eImroyC19GCozn8=   
   =Sf20   
   -----END PGP SIGNATURE-----   
      
   --    
   "Always do the right thing: It will delight /  Aluminum Foil Deflector   
   Beanies     
   some and astound the rest" - Mark Twain    / Psychotronic protection, low   
   prices   
      
   "Anyone who uses the term 'intellectual property' is either confused or trying   
   to confuse you." - Richard Matthew Stallman   
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)