• Another update to clrghouz

    From deon@21:2/116 to All on Sat Jun 1 10:52:30 2024
    Howdy,

    I've had a niggling issue for a while with how clrghouz processes messages and tic files, where the text has high ascii characters. While clrghouz could handle it OK, the DB complained of UTF8 encoding issues when saving records with those characters. My workaround for that wasnt great, and actually was snowballing another issue that I was writing work arounds for...

    Most times there were no issues - since most of the messages here didnt trigger the issue (except the occassional FSX_DAT, which has binary data).

    So I've reworked that part of my code, and another situation of why didnt I do it this way the first time (time will remind me why I didnt).

    So (hopefully) you shouldnt see any issues with message processing, but if something seems strange let me know.


    ...ëîåï
    --- SBBSecho 3.20-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Warpslide@21:3/110 to deon on Fri May 31 17:00:32 2024
    On 01 Jun 2024, deon said the following...

    So (hopefully) you shouldnt see any issues with message processing, but
    if something seems strange let me know.


    ...ëîåï

    Hmm, normally your signature looks like a stylized "deon", but now it looks like the above. Here's a screenshot of what I see here:

    https://postimg.cc/9R8SRVSZ

    Not sure if it's related to this change.


    Jay

    ... Nostalgia is OK, but it's not what it used to be

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (21:3/110)
  • From AKAcastor@21:1/162 to Warpslide on Fri May 31 18:51:38 2024
    ...ëîåï

    Hmm, normally your signature looks like a stylized
    "deon", but now it looks like the above. Here's a
    screenshot of what I see here:
    https://postimg.cc/9R8SRVSZ

    On my system (which supports only CP 437 as I am living in early-90s MS-DOS) the signature looked correct. "...ëîåï"

    Kludges that I see on deon's message:
    TZUTC: 1000
    MSGID: 3711.fsx_net@21:2/116 2abfb54e
    PID: Synchronet 3.20a-Linux master/7b932f63e Dec 9 2023 GCC 10.2.1
    TID: SBBSecho 3.20-Linux master/7b932f63e Dec 9 2023 GCC 10.2.1
    COLS: 80
    BBSID: ALTERANT
    CHRS: CP437 2
    NOTE: FSEditor.js v1.105

    Kludges that I see on Warpslide's message:
    TZUTC: -0400
    MSGID: 21:3/110 cdbc3c37
    REPLY: 3711.fsx_net@21:2/116 2abfb54e
    TID: clrghouz 81f59dcb
    DBID: 505059


    I don't know if there's any useful information here, just wanted to share that "it works on my end" but my system doesn't know anything besides CP437. I don't know much about CHRS kludges but "it seems right" I think?


    Chris/akacastor

    --- Maximus 3.01
    * Origin: Another Millennium - Canada - another.tel (21:1/162)
  • From Exodus@21:1/144 to Deon on Fri May 31 22:06:48 2024
    ...ëîåï

    Looks fine over here.

    ... Drink till she's cute. Stop before you get married.

    --- Renegade v1.35à/DOS
    * Origin: The Titantic BBS Telnet - ttb.rgbbs.info (21:1/144)
  • From deon@21:2/116 to Warpslide on Sat Jun 1 12:30:40 2024
    Re: Re: Another update to clrghouz
    By: Warpslide to deon on Fri May 31 2024 05:00 pm

    Howdy,

    ...‰Œ†‹
    Hmm, normally your signature looks like a stylized "deon", but now it looks like the above. Here's a screenshot of what I see here:

    Yes, it will be related. Thanks.

    Looks like I might need to think this through more...


    ...ëîåï
    --- SBBSecho 3.20-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From deon@21:2/116 to AKAcastor on Sat Jun 1 17:06:46 2024
    Re: Re: Another update to clrghouz
    By: AKAcastor to Warpslide on Fri May 31 2024 06:51 pm

    Howdy,

    I don't know if there's any useful information here, just wanted to share that "it works on my end" but my system doesn't know anything besides CP437. I don't know much about CHRS kludges but "it seems right" I think?

    Yup, helpful thanks.

    The CHRS kludge helps (some) BBSs render the message according to the terminal/charset. Most of us using a terminal will be CP437...


    ...ëîåï
    --- SBBSecho 3.20-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Ogg@21:4/106.21 to Warpslide on Sat Jun 1 19:36:00 2024
    Hello Warpslide!

    https://postimg.cc/9R8SRVSZ

    That doesn't show up for me. It seems to be an .avif file.
    Never heard of that one. temp-Image-X8-J0h3.avif


    --- OpenXP 5.0.58
    * Origin: Ogg's WestCoast Point (21:4/106.21)
  • From Warpslide@21:3/110 to Ogg on Sat Jun 1 18:52:36 2024
    On 01 Jun 2024, Ogg said the following...

    https://postimg.cc/9R8SRVSZ

    That doesn't show up for me. It seems to be an .avif file.
    Never heard of that one. temp-Image-X8-J0h3.avif

    Try this one:

    https://postimg.cc/sGp74YHW


    The first one is a screenshot from my Mac which I think was in heic format. This one should be a jpg.


    Jay

    ... I was addicted to the hokey pokey, but I turned myself around

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (21:3/110)
  • From Ogg@21:4/106.21 to Warpslide on Sun Jun 2 08:17:00 2024
    Hello Warpslide!

    https://postimg.cc/9R8SRVSZ

    That doesn't show up for me. It seems to be an .avif file.
    Never heard of that one. temp-Image-X8-J0h3.avif

    Try this one:

    https://postimg.cc/sGp74YHW


    The first one is a screenshot from my Mac which I think was in heic
    format. This one should be a jpg.

    Same thing. But, I found the problem. I was trying to view
    the postimg.cc site with MyPal and/or PaleMoon on my XT where I
    operate OpenXP for messaging.

    The links work fine on my Win7 pc with FF.

    It seems that this "ancient" BBS stuff is becoming increasingly
    more and more difficult unless newer software is in the mix.
    :(

    It's an interesting dichotomy that is getting tedious to
    manage.

    FYI, imgbb.com cooperates with MyPal and PaleMoon though.

    --- OpenXP 5.0.58
    * Origin: Ogg's WestCoast Point (21:4/106.21)