• GoldED and Synchronet Question

    From Digital Man@1:103/705 to Accession on Thu Nov 6 16:22:10 2025
    Re: GoldED and Synchronet Question
    By: Accession to Digital Man on Thu Nov 06 2025 04:35 pm

    Hey Digital!

    On Wed, 05 Nov 2025 18:00:44 -0800, you wrote:

    Packing and renumbering are 2 different things. Packing should have no effect on Golded. And a sysop shouldn't renumber any message base
    without a very good reason.

    The default timed event for '%!smbutil% mp100 /path/to/sbbs/data/subs/*.shd' definitely has a bad effect on Golded. I imagine it probably has to do with deleting olds messages, messages over max, and renumbering the messages.

    Technically that command doesn't renumber of the messages. I believe it could be messing up Golded, but it's not due to renumbering.

    If
    your max is 2000 messages, the 2014th message in the area that gets posted before smbutil is ran, gets changed to message number 2000.

    Each message has a unique monotonically-increasing number that's not changed by maintaining or packing a message base. 'fixsmb' has a -renumber option (which understably would have a bad effect on Golded), smbutil doesn't have that option.

    All I was saying is that needs to be disabled or Golded will spaz out the next time you run it after smbutil runs.

    Gotcha.
    --
    digital man (rob)

    Sling Blade quote #2:
    Karl (re: killing Doyle): I hit him two good whacks in the head with it.
    Norco, CA WX: 69.2øF, 63.0% humidity, 5 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.31-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Accession@1:103/705 to Digital Man on Fri Nov 7 17:29:26 2025
    Hey Digital!

    On Thu, 06 Nov 2025 16:22:10 -0800, you wrote:

    Technically that command doesn't renumber of the messages. I believe it could be messing up Golded, but it's not due to renumbering.

    Ok. Yeah, it definitely messes up Golded.

    On the other hand, any newsreader I've used with Synchronet doesn't have an issue with the smbutil event.

    If
    your max is 2000 messages, the 2014th message in the area that gets
    posted before smbutil is ran, gets changed to message number 2000.

    Each message has a unique monotonically-increasing number that's not
    changed by maintaining or packing a message base. 'fixsmb' has a
    -renumber option (which understably would have a bad effect on Golded), smbutil doesn't have that option.

    Understood, and no.. I've never used that fixsmb option. I would imagine that the last read pointers move and Golded doesn't know they moved, or something. The same happens when using Golded to read /sbbs/data/mail. When an event of some sort kills read mail (or maybe it's killed after 30 days or something), Golded craps the bed there, too.

    I just chalk it up as Golded's Synchronet support not being updated. Besides the one fix Vitaliy did somewhat recently, and the patches you've made somewhat recently.. nobody has updated that code in ages. *shrug*

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    # Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (723:1/1)
    ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)