From: muta...@gmail.com   
      
   On Friday, June 18, 2021 at 8:21:29 AM UTC+10, Joe Monk wrote:   
   > > > NNTP is a TCP application. So it needs TCP/IP.    
   > > As far as I can tell, that is not true.    
   > >    
   > > I am aiming to have a news reader that does:    
   > >    
   > > fopen("nntp://eternal-september.org", "r+");    
   > >   
   > NNTP = TCP port 119. HTTP = TCP port 80. HTTPS = TCP port 443. SSH = TCP   
   port 22. Telnet = TCP Port 23.    
   >    
   > "NNTP is a text-based protocol and allows for the alternating exchange   
   between client and server: Therefore, for every NNTP inquiry, an NNTP reply is   
   expected. For this communication the IANA (Internet Assigned Numbers   
   Authority) has provided TCP-Port    
   119, which in this case is solely reserved for the transfer protocol – a   
   TCP/IP network such as the Internet is as a result the underlying basis for   
   the information platform. The NNTP itself has access to the application layer   
   and for this relies    
   directly on the TCP protocol, which has the advantage of ensuring both a   
   secure and reliable transfer of data."    
   >    
   > https://www.ionos.com/digitalguide/server/know-how/nntp-networ   
   -news-transfer-protocol/    
      
   Yes, and it's all a scam.   
      
   It's just a normal BBS you can dial. I could have put the   
   exact same text out from my own BBS way back in the   
   90s when I was running a BBS.   
      
   No properly-written news reader should be able to tell   
   the difference whether their news server was my 1990s   
   BBS or Eternal September in 2021.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)