1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • webv4 - Read Messages

    From Gregg Somes@1:103/705 to GitLab issue in main/sbbs on Fri Feb 26 08:03:19 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/229

    I have noticed that when viewing subs with 001-formum.ssjs; when reading messages in any sub (ie ?page=001-formum.ssjs&sub=dove-syncdisc) all of the messages in that sub are marked as read and do not display message counters in that sub after the page is refreshed, even messages that have nopt been read.
    --- SBBSecho 3.13-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From echicken@1:103/705 to GitLab note in main/sbbs on Fri Feb 26 11:40:24 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/229#note_1659

    TL;DR: We don't have per-message-per-user read/unread status in Synchronet.webv4 considers a message "new" if its number is greater than your scan pointer for that sub. If you have ten unread messages in a sub, then read the newest one, your scan pointer now points to the newest message. Everything older (including the nine previously "unread" messages) is considered "read".I didn't want to twiddle scan pointers from the web because of this, but people insisted, so now we have this shitty feature. I can maybe make it turn-offable.I am considering different ways of dealing with this in the new forum XJS page, including a "new message scan" view, but we'll see how that works out.001-forum.ssjs will be phased out soon either way.
    --- SBBSecho 3.13-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From echicken@1:103/705 to GitLab issue in main/sbbs on Fri Feb 26 11:40:24 2021
    close https://gitlab.synchro.net/main/sbbs/-/issues/229
    --- SBBSecho 3.13-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)