1. Forum
  2. DOVE-Net
  3. Synchronet Sysops Only

  • MRC: display still not fixed even after update

    From Nigel Reed@VERT to GitLab issue in main/sbbs on Thursday, March 06, 2025 23:45:59
    open https://gitlab.synchro.net/main/sbbs/-/issues/885

    ![image](https://gitlab.synchro.net/main/sbbs/uploads/3da92ddd311839f8779f8db843eacd5c/image.png){width=778 height=33}

    This doesn't make grammatical sense and there's that SERVER at the end in green?

    "Your handle is trusted from this BBS (Expires in 4wks) "
    Why not just say 4 weeks?

    Seems I cannot assign it to codefenix.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Craig Hendricks@VERT to GitLab note in main/sbbs on Friday, March 07, 2025 05:17:09
    https://gitlab.synchro.net/main/sbbs/-/issues/885#note_6731

    These are messages returned from the **MRC server**, and are not controlled within this or any other MRC clients. I can explain them though.

    For the first one, there is supposed to be a break between the words "rooms" (the end of one server message) and "SERVER" (the start of the next server message). I've informed StackFault of this issue, and recently sent him a reminder.

    For the second one, StackFault simply made a decision to use shorthand to express the trusted handle expiration. He runs the MRC server; that's his prerogative.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Craig Hendricks@VERT to GitLab issue in main/sbbs on Friday, March 07, 2025 05:17:10
    close https://gitlab.synchro.net/main/sbbs/-/issues/885

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Deucе@VERT to GitLab note in main/sbbs on Friday, March 07, 2025 07:42:02
    https://gitlab.synchro.net/main/sbbs/-/issues/885#note_6732

    I have no horse in this race, I just wanted to point out that the client can manipulate text it displays.

    ```
    lineFromServer.replace(/roomsSERVER/, "rooms\r\nSERVER");
    ```

    Chasing time abbreviation is likely more painful and not worth it, but also possible.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Craig Hendricks@VERT to GitLab note in main/sbbs on Friday, March 07, 2025 08:04:59
    https://gitlab.synchro.net/main/sbbs/-/issues/885#note_6733

    I would not attempt to manipulate incoming messages at all.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Craig Hendricks@VERT to GitLab note in main/sbbs on Friday, March 07, 2025 08:22:20
    https://gitlab.synchro.net/main/sbbs/-/issues/885#note_6733

    I would not attempt to manipulate incoming messages at all.

    Edited to elaborate: each part of the incoming message packet has special meaning. The "SERVER" is the "from_user" field in the beginning of the next packet. Simply inserting a CR-LF in front of "SERVER" does not fix the problem, because the remaining packet string would need to be processed by the client separately from the proceeding packet. Besides, it's incomplete since the two meshed packets exceed the legal length of one packet anyway.

    For the record, the Mystic clients see the same faulty startup message too.

    TL;DR: The server needs to fix what it's sending out.

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