• exec/load/logonlist_lib.j

    From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Sun Jun 9 17:51:00 2024
    https://gitlab.synchro.net/main/sbbs/-/commit/8307cbeaea8c402f5b7bda6c
    Modified Files:
    exec/load/logonlist_lib.js
    Log Message:
    When pulling from previous days to fulfill the "last few callers list", insert

    Insert (using unshift) to the beginning of the list, rather than append (using push) to the end of the list.

    This fixes issue #761

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rob Swindell (on Debian L@VERT to Git commit to main/sbbs/m on Sun Jun 9 18:52:00 2024
    https://gitlab.synchro.net/main/sbbs/-/commit/16c5298fa047acd7051ccece
    Modified Files:
    exec/load/logonlist_lib.js exec/logonlist.js
    Log Message:
    Log the current connection protocol as a separate property in logon.jsonl

    Accession reported that (sometimes?) his NNTP logins show up in his
    logon.jsonl files. This is most likely just a race condition when logging
    in close to the same time with multiple protocols (e.g. Telnet and NNTP
    in this case). So, let's log the client.protocol as a separate JSON property and not require on the user.connection property (which is overwritten for *every* login, for almost all connection/server types, not just the terminal server). The client.protocol is always correct for the current session running the script.

    An NNTP login should never appear in the logon.json file.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net