Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_SYSOPS    |    Synchronet Multinode BBS Software Suppor    |    33,243 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 30,251 of 33,243    |
|    dragon to Nightfox    |
|    Re: Bink Polling    |
|    31 Aug 24 22:59:42    |
      TZUTC: -0400       MSGID: 56227.sync_sys@1:103/705 2b39f837       REPLY: 56226.sync_sys@1:103/705 2b39b23e       PID: Synchronet 3.17c-Win32 Oct 8 2019 MSC 1922       TID: SBBSecho 3.20-Linux master/46c603ce3 Aug 26 2024 17:07 GCC 12.2.0       BBSID: IPTIA       CHRS: UTF-8 4       On 8/31/2024 18:46, Nightfox wrote:       > Re: Re: Bink Polling       > By: dragon to Nightfox on Fri Aug 30 2024 06:27 pm       >        > > dr>> BINKPOLL Timed out receiving packet data from remote:       >        > > dr>> I edited binkp.js and tripled the this.timeout setting to no       effect.       >        > >> You're running a fairly old version of Synchronet. The issue you're       seeing       > >> may well have been fixed in a newer version, so it would be good to       > >> upgrade. The latest is 3.19 (January 2022), but the latest development       > >> version, 3.20, has been stable for quite a while.       >        > dr> I was more hoping for a setting or something I had overlooked. Perhaps       > dr> this has been fixed, but if I am one of the few experiencing this       issue,       > dr> it may not be on anyone's RADAR.       >        > If by chance it has already been fixed in a newer version though, I'd think       the answer would be to update to the newer version..?       >        > Nightfox       >        > ---       > � Synchronet � Digital Distortion: digitaldistortionbbs.com              I like to know the "why" of things. I would also like confirmation that        the issue is known and fixed instead of just doing an uprade with my        fingers crossed.              It turns out that this issue must have been discovered in the past,        because I found a change in the binkp.js file that addresses the issue.              In the version that comes with 3.16, if the remote sends a zero length        packet, the whole session is abended. In the version currently supplied        with 3.20, a warning is logged and the session continues.              I replaced binkp.js and binkit.js with the current versions, and things        appear to be working.              BTW, my Fidonet host is running version 3.15.              ---        þ Synchronet þ IPTIA - bbs2.ipingthereforeiam.com:2323        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 10/0 1 90/1 102/401 103/1 17 705 105/81 106/201 124/5016       SEEN-BY: 153/7715 214/22 218/0 1 215 601 700 720 840 860 870 880 930       SEEN-BY: 226/30 227/114 229/110 114 206 317 400 426 428 470 550 700       SEEN-BY: 229/705 266/512 280/464 282/1038 291/111 301/1 320/219 322/757       SEEN-BY: 342/200 396/45 460/58 633/280 712/848 5075/35       PATH: 103/705 218/700 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca