Subj : a classic QWK areas shifting problem
To   : mark lewis
From : Rob Swindell
Date : Mon Feb 07 2022 01:17:22

  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)

.