• preformat gopher results to assist broken clients

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Thu Dec 21 19:58:29 2023
    open https://gitlab.synchro.net/main/sbbs/-/issues/689

    I've tried 4 different clients and each of them render the gopher results differently. It would help to pre-format the article so maybe help some of these clients.

    post in the BBS: ![image](https://gitlab.synchro.net/main/sbbs/uploads/16e974a426da120aa6a0983ba492b927/image.png)

    Post in lynx via putty 80x24: ![image](https://gitlab.synchro.net/main/sbbs/uploads/93fa14b0aba14eebbebfad2f1af251ff/image.png)

    Post in Gophie: ![image](https://gitlab.synchro.net/main/sbbs/uploads/9bf3c647f3a58b0c4ef3aa9bd5100bde/image.png)

    Post in Gopher Browser (just one very long line) ![image](https://gitlab.synchro.net/main/sbbs/uploads/192d90196ba9dfad90489cef89bce932/image.png)

    Post in Simple Gopher Client ![image](https://gitlab.synchro.net/main/sbbs/uploads/84dd308a6764635014c506c18f2d4b0b/image.png)
    --- 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 Thu Dec 21 20:12:58 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/689#note_4584

    Is it possible there's something weird with that message? Do all messages appear this way or only those imported from a specific FTN hub or posted by a specific FTN node?

    A hex dump of the message would help to determine what's going on here. You can do this msglist.js (not sure about DDMessageReader) or by hex-dumping the right region of the data/subs/*.sdt file.
    --- 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 Fri Dec 22 10:07:13 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/689#note_4598

    Shouldn't be. I wrote it with Deuce's editor. I'll get a hex dump for you later.
    --- 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 Fri Dec 22 10:55:03 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/689#note_4600

    ```
    000: 47 72 65 65 74 69 6E 67 - 73 20 61 6C 6C 2C 20 20 Greetings all,
    010: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    020: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    030: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    040: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    060: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    070: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    080: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 20 20
    090: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 4C 69 Li
    0a0: 6E 75 78 4E 65 74 20 69 - 73 20 62 61 63 6B 20 75 nuxNet is back u
    0b0: 6E 64 65 72 20 6E 65 77 - 20 6F 77 6E 65 72 73 68 nder new ownersh
    0c0: 69 70 2E 20 54 68 61 6E - 6B 73 20 74 6F 20 6E 75 ip. Thanks to nu
    0d0: 67 61 78 20 61 74 20 54 - 68 65 20 42 79 74 65 20 gax at The Byte
    0e0: 45 78 63 68 61 6E 67 65 - 20 42 42 53 20 77 68 6F Exchange BBS who
    ```

    I'm pretty sure I did not put those spaces in there. That wouldn't make any sense whatsoever.

    I went in to edit the message and there is one space after the , - it would beep at me so no more characters if I tried to cursor right. If I press DEL then it brings the line below next to the ,. So something is putting in spaces where there shouldn't be. It's not me.

    After saving the message, all the spaces are now gone and it seems to be rendering ok. Very odd.
    --- 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 Sun Dec 31 14:46:49 2023
    close https://gitlab.synchro.net/main/sbbs/-/issues/689
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)