MSGID: 2:221/1.1 5eb6dd03   
   PID: nntpPoint 2.0.5.40   
   REPLY: 2:280/464.47 5eb69fb4   
   RFC-References: <849cb096@p0.f360.n221.z2.ftn> <5eb69fb4@p47.f464.n280.z2.ftn>   
   RFC-From: Tommi Koivula    
   RFC-MIME-Version: 1.0   
   TZUTC: 0300   
   RFC-In-Reply-To: <5eb69fb4@p47.f464.n280.z2.ftn>   
   RFC-Content-Type: text/plain; charset=UTF-8   
   CHRS: UTF-8 4   
   RFC-Content-Language: en-US   
   RFC-Content-Transfer-Encoding: 7bit   
   On 9.5.2020 14:19, Oli wrote:   
      
   > As I wrote, I'm interested in support for other flags, like IBNS   
   > (for binkps), IBNQ (binkp over QUIC), IBNO (for Onion addresses),   
   > etc. I also would like to dynamically use SOCKS servers for the   
   > different encrypted protocols. Using the perl hook for the nodelist   
   > processing would be much more flexible and straight forward. The   
   > only thing that is missing in binkd is the ability to set the -pipe   
   > parameter in perl.   
   >    
   > No need to discuss how useful or unnecessary this is, it's only   
   > experimental ;)   
      
   Sounds interesting. :) I'm only supporting IBNS at the moment...   
      
   'Tommi   
      
   --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101   
   Thunderbird/68.8.0   
    * Origin: rbb nntp point system (2:221/1.1)   
   SEEN-BY: 1/123 90/1 103/705 120/340 601 154/10 203/0 221/1 6 242 360   
   SEEN-BY: 226/30 227/114 702 229/101 200 426 664 1014 230/0 240/2100   
   SEEN-BY: 240/5138 5832 5853 6309 249/109 307 317 280/464 5003 5555   
   SEEN-BY: 288/100 292/854 8125 310/31 320/219 342/200 396/45 423/81   
   SEEN-BY: 423/120 712/848 770/1 2432/390 2452/250 2454/119   
   PATH: 221/1 280/464 240/5832 229/426