• Checking

    From Charles Pierson@4:902/26.52 to All on Tue Oct 12 07:03:18 2021
    Hello, All.

    I think my feed is broken here.

    --
    Best regards!
    Posted using Hotdoged on Android
    --- Hotdoged/2.13.5/Android
    * Origin: Houston, TX (4:902/26.52)
  • From Wilfred van Velzen@2:280/464 to Stas Mishchenkov on Tue Oct 12 14:29:18 2021
    Hi Stas,

    On 2020-10-12 15:26:41, I wrote to Charles Pierson:

    @MSGID: 2:460/58 00000351
    @REPLY: 2:460/58 00000350
    @PID: tg2fido_gate_v0.6.1
    @INTL 4:902/26 2:460/58
    @TOPT 52
    @CHRS: CP866 2
    @TGUID: 202096118
    @REPLYTO 2:280/464
    @RealName: Wilfred van Velzen 2:280/464
    Hello, All.

    I think my feed is broken here.

    --
    Best regards!
    Posted using Hotdoged on Android
    Telegram side works fine too!

    This is confusing though! The quoted message isn't quoted, and my new text is directly behind it, so you can't differentiate between them...

    --- tg2fido gate v0.6.1
    * Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)
    @PATH: 460/58 221/6 1 280/464

    Bye, Wilfred.
    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Charles Pierson on Tue Oct 12 15:27:54 2021
    Hi Charles,

    On 2020-10-12 15:48:06, you wrote to me:

    Hi Stas, On 2020-10-12 15:26:41, I wrote to Charles Pierson: WvV>
    @MSGID: 2:460/58 00000351 WvV> @REPLY: 2:460/58 00000350 WvV> @PID:
    tg2fido_gate_v0.6.1 WvV> @INTL 4:902/26 2:460/58 WvV> @TOPT 52 WvV>
    @CHRS: CP866 2 WvV> @TGUID: 202096118 WvV> @REPLYTO 2:280/464 WvV>
    @RealName: Wilfred van Velzen 2:280/464 CP>> Hello, All. WvV> I
    think my feed is broken here. WvV> -- WvV> Best regards! WvV> Posted
    using Hotdoged on Android WvV> Telegram side works fine too! This is
    confusing though! The quoted message isn't quoted, and my new text
    is directly behind it, so you can't differentiate between them...

    I hadn't noticed that before. However in this message it is flagging parts of my message as yours.

    That's the problem. And should be avoided!

    Bye, Wilfred.
    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Charles Pierson on Tue Oct 12 15:34:00 2021
    Hi Charles,

    On 2020-10-12 16:06:10, you wrote to August Abolins:

    I noticed on the quoting. Primarily on Wilfred's replies to me. He
    said it's strange from his view. Nothing has looked different to me though, other than his replies not seeming to assign the correct id
    tags on the quotes.

    That's exactly the problem if you reply from the telegram side to a longer message.

    Bye, Wilfred.
    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Charles Pierson@2:240/1120.976 to Wilfred van Velzen on Tue Oct 12 08:49:28 2021
    Hello, Wilfred van Velzen.
    On 10/12/20 3:27 PM you wrote:

    I hadn't noticed that before. However in this message it is
    flagging parts of my message as yours.
    That's the problem. And should be avoided!

    Definitely.

    --
    Best regards!
    Posted using Hotdoged on Android
    --- Hotdoged/2.13.5/Android
    * Origin: Houston, TX (2:240/1120.976)
  • From Charles Pierson@2:240/1120.976 to Wilfred van Velzen on Tue Oct 12 08:54:34 2021
    Hello, Wilfred van Velzen.
    On 10/12/20 3:34 PM you wrote:

    I noticed on the quoting. Primarily on Wilfred's replies to me.
    He said it's strange from his view. Nothing has looked different
    to me though, other than his replies not seeming to assign the
    correct id tags on the quotes.
    That's exactly the problem if you reply from the telegram side to
    a longer message.

    Yeah, that's a thing with being able to trim messages between. Not sure about a way around it.

    --
    Best regards!
    Posted using Hotdoged on Android
    --- Hotdoged/2.13.5/Android
    * Origin: Houston, TX (2:240/1120.976)
  • From Wilfred van Velzen@2:280/464 to Charles Pierson on Tue Oct 12 16:20:28 2021
    Hi Charles,

    On 2020-10-12 08:54:34, you wrote to me:

    I noticed on the quoting. Primarily on Wilfred's replies to me.
    He said it's strange from his view. Nothing has looked different
    to me though, other than his replies not seeming to assign the
    correct id tags on the quotes.
    That's exactly the problem if you reply from the telegram side to
    a longer message.

    Yeah, that's a thing with being able to trim messages between. Not sure about a way around it.

    Stas should fix the gate software, so it quotes the hole Telegram message not just the first line.

    Bye, Wilfred.
    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Charles Pierson@2:240/1120.976 to Brother Rabbit on Tue Oct 12 09:57:14 2021
    Hello, Brother Rabbit.
    On 10/12/20 5:39 PM you wrote:

    Hello, Wilfred van Velzen. On 10/12/20 3:34 PM you wrote: CP>> I
    noticed on the quoting. Primarily on Wilfred's replies to me.
    He said it's strange from his view. Nothing has looked
    different CP>> to me though, other than his replies not seeming
    to assign the CP>> correct id tags on the quotes.
    That's exactly the problem if you reply from the telegram side to
    a longer message.
    Yeah, that's a thing with being able to trim messages between.
    Not sure about a way around it.

    Unfortunately, it is not so easy to avoid overclocking when
    answering from Telegram. Of course, I can cut lines containing
    more than one ">" at the beginning, but this can lead to very
    bizarre errors in the text.

    Exactly. I don't see an obvious solution. Not an automated one, in any case.

    --
    Best regards!
    Posted using Hotdoged on Android
    --- Hotdoged/2.13.5/Android
    * Origin: Houston, TX (2:240/1120.976)
  • From Benny Pedersen@2:230/0 to Wilfred van Velzen on Mon Oct 18 15:32:26 2021
    Hello Wilfred!

    12 Oct 2020 14:25, Wilfred van Velzen wrote to Charles Pierson:

    I think my feed is broken here.
    Fido side is working fine...

    +1


    Regards Benny

    ... there can only be one way of life, and it works :)
    --- Msged/LNX 6.1.2 (Linux/5.9.0-gentoo-x86_64 (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)