1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • Add better way for user defined node status

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Wed Sep 6 09:31:55 2023
    open https://gitlab.synchro.net/main/sbbs/-/issues/618

    With more people writing scripts, authors may want to include their own node status for their programs.We discussed this a few years ago and the solution was to use unused text.dat numeric 708 along with NODE_BXFR which you said wasn't used at that time.However, webv4 shows "transferring bidirectional" when I have set 708 to be "Multi Relay Chat". It appears that NODE_BXFR is hard coded in several places.The solution might be to just fix webv4 so that it pulls the currently running program from the node information.Maybe node.ini could contain an "nodeinfo" entry that's updated so it can be easily accessedEither way, webv4 definitely needs fixing to read the proper value that was set.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Sep 6 17:22:29 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/618#note_3916

    webv4 just needs to read the extended node status from the node.exb file (e.g. use the extended_status() function from presence_lib.js?) when appropriate.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Sat Sep 9 10:27:38 2023
    close https://gitlab.synchro.net/main/sbbs/-/issues/618
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Sat Sep 9 22:25:28 2023
    reopen https://gitlab.synchro.net/main/sbbs/-/issues/618

    With more people writing scripts, authors may want to include their own node status for their programs.We discussed this a few years ago and the solution was to use unused text.dat numeric 708 along with NODE_BXFR which you said wasn't used at that time.However, webv4 shows "transferring bidirectional" when I have set 708 to be "Multi Relay Chat". It appears that NODE_BXFR is hard coded in several places.The solution might be to just fix webv4 so that it pulls the currently running program from the node information.Maybe node.ini could contain an "nodeinfo" entry that's updated so it can be easily accessedEither way, webv4 definitely needs fixing to read the proper value that was set.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Sat Sep 9 22:28:11 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/618#note_3938

    Not even close.jsexec nodelistNode 1: Nelgin (52 M) in chat section via ssh [EQ]node statusNode 1: User #1 in chat section via ssh [QE]webv4![image](/uploads/10c765a2b1d1a078611890395da7f1c8/image.png)
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rick Parrish@1:103/705 to GitLab note in main/sbbs on Sun Sep 10 06:56:59 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/618#note_3940

    What did Who's Online output prior to the change? As you can see from the commit, it only changed the value of the action property: https://gitlab.synchro.net/main/sbbs/-/commit/f1591f88bc5661689fa64c65fa5d2da7281656e6#4816d613f6f3d6ae578a67095746d1a4b8b2f536_87_89This data is then used in 001-nodelist.xjs, which should only skip outputting a node if the user or action is null: https://gitlab.synchro.net/main/sbbs/-/blob/master/webv4/sidebar/001-nodelist.xjs#L29So maybe node_status is returning null for you for some reason, and needs fixing? It seems to be working OK here:![image](/uploads/d64794017f46373192b6e4481fffe7b1/image.png)
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)