home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   CONSPRCY      How big is your tinfoil hat?      2,445 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 262 of 2,445   
   Rob Swindell to mark lewis   
   a classic QWK areas shifting problem   
   07 Feb 22 01:17:22   
   
   TZUTC: -0800   
   MSGID: 3207.consprcy@1:103/705 26662629   
   REPLY: 1:3634/12.73 6200d01a   
   PID: Synchronet 3.19c-Win32 master/b35a99076 Feb  6 2022 MSC 1929   
   TID: SBBSecho 3.14-Linux master/9e8dbe4e1 Feb  6 2022 GCC 8.3.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: a classic QWK areas shifting problem   
     By: mark lewis to August Abolins on Mon Feb 07 2022 02:40 am   
      
    >   
    >  On 2022 Feb 06 13:24:00, you wrote to me:   
    >   
    >  SD>>>>> MMMMM----- Recipe via Meal-Master (tm) v8.06   
    >  SP>>> Hmm wrong board for this isnt it 8)   
    >   
    >  ml>> this was a classic QWK areas shifting problem that happens when areas   
    >  ml>> are added or moved... if QWK used actual area tags instead of   
    >  ml>> numbers, this wouldn't happen but it is long past the time when this   
    >  ml>> could have been fixed in the implementation...   
    >   
    >  AA> QWK system/distribution has "classic" problems?   
    >   
    > it is a long-standing (aka classic) problem for QWK setups... QWK uses   
    > message area numbers to identify message areas... if a BBS adds a message   
    > area, all the areas after it are pushed down another number... so when a   
    > user has written a message in area #4 and the BBS has added a new area as   
    > #3, the user's message is posted to the new #4 instead of the old one which   
    > is now #5...   
      
   Some BBSes may work that way, but not all. Synchronet, for example, has long   
   supported 'static QWK conference number' assignment, so re-arrangement of   
   message areas by the sysop does not have to mess-up users' (or QWKnet nodes')   
   pending REP packets (resulting in the problem you described).   
   --    
                                               digital man (rob)   
      
   This Is Spinal Tap quote #25:   
   Viv Savage: Have... a good... time... all the time. That's my philosophy.   
   Norco, CA WX: 60.1øF, 18.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.14-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 633 987 120/340 123/131 124/5014   
   SEEN-BY: 124/5016 129/305 330 331 153/7715 226/30 227/114 229/110   
   SEEN-BY: 229/206 317 400 424 426 428 664 700 240/5832 266/512 280/464   
   SEEN-BY: 282/1038 301/1 317/3 320/219 322/757 342/200 387/25 26 28   
   SEEN-BY: 396/45 460/58 712/848   
   PATH: 103/705 280/464 396/45 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca