REPLY: 2:221/360.0 5e0d9e1e   
   MSGID: 2:5015/46 5e0e0ecb   
   CHRS: CP866 2   
   TZUTC: 0300   
   TID: hpt/lnx 1.9.0-cur 17-02-17   
   Hello, Tommi!   
      
   Thursday January 02 2020 09:39, from Tommi Koivula -> Nil Alexandrov:   
      
    >> Should we continue using smapinntpd then?   
    TK> That might be a good idea. At least in 64bit linux.   
      
   Looks like smapi version is the logical continuation of the project, though   
   could have been done as a build option, link with JAMLIB or SMAPI. Hope can use   
    this echo conference for SmapiNNTPd related stuff.   
      
   Here's my list of TODO ;-)   
      
   * Socket reuse (just one line fix, otherwise you need to wait a few mins after   
   restart).   
      
   * Message-id passed in <> brackets (some NNTP clients use message-id to fetch   
   head/body/article instead of the article number, e.g. lynx text-mode browser   
   works with nttp:// URL scheme).   
      
   * Add encoding support in subjects (some NNTP clients even use a different   
   encoding in subject than the body itself, e.g. Thunderbird will always use utf8   
    in subjects (Subject: =?UTF-8?Q) even though the body encoding is 8 bit)   
      
   * Add utf8 support for posting.   
      
   * Maybe get rid of charset files completely, just compile with libiconv or ICU.   
      
   * Having been integrated with Husky project, specifically with SMAPI library,   
   so why not using the fidoconf to read out groups.   
      
   Best Regards, Nil   
   --- GoldED+/LNX 1.1.5   
    * Origin: -=NIL BBS=- (2:5015/46)   
   SEEN-BY: 1/123 57/0 90/1 153/250 154/10 203/0 220/70 221/0 227/114   
   SEEN-BY: 229/426 452 1014 240/5832 249/206 317 267/800 280/464 5003   
   SEEN-BY: 280/5555 310/31 317/3 322/757 342/200 770/0 1 100 340 772/0   
   SEEN-BY: 772/1 210 500   
   PATH: 5015/46 5020/1042 261/38 153/7715 250 770/1 310/31 280/464   
   PATH: 229/426