Hi Charles!
13 Oct 20 02:36, you wrote to me:

Think of it like sending out a mass email that has a mistake in it.
You can recall the email and send a corrected one. However, if someone
has already READ that email, the recall fails.

I hear ya. BUT, in this case Telegram on its own allows re-editing. That's quite different than email which can't be undone. I just thought that if the Fidobot could just slow down then the advantage of Telegram's re-edit function would be utilized - that would be a fine *feature* (or selling point) to capitalize on and not lose.

However, I recognize Stas' approach to just process the message as soon as it's detected.

In this case, the Gatebot has "read" the message and has it cued for tranfer.

It doesn't have to read it right away. Maybe it could wait to give us poor grammar and spelling persons to adjust something if required.

I believe Stas said the transfers happen every minute. In that case,
yes it's basically a done deal once you hit send, although it is
deleted on the Telegram side.

Correct. Right now it is programmed to check every minute. But that is up to the Fidobot, not when I "sent" it to Telegram.

If there were clearly defined "tossing/grabbing" intervals for the
bot, then there is some confidence to re-edit the message before
the fido side sees it.

Unfortunately, that's not how things work with this system.

But that part is programmable and doesn't *have* to be that way. It's not entirely unfortunate either. I appreciate Stas' interest to detect ASAP and deal with it. But if detection was slowed down, then the advantage of Telegram's re-edit function would not be lost.

Personally, I would try to capitalize on a new technology offering a features and not diminish it if there was a choice.

I'll just have to wrap my head around the fact that once I press
Send in TgM, then it is unalterable, ...

I almost always think that way. Once I'm done composing and hit send,
it's done. Corrections may follow if necessary.

Maybe it will make me more conscious of my spelling. I'll try to deal with it.


---
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net)

Hi, August!

12 ��� 20 23:50, August Abolins -> Brother Rabbit:

But while the message is on the TgM servers, it *can* be edited. The reason why it can't be edited (and I don't expect it to be) is when
the robot grabs it.

You're wrong. A new message of a different type will be created, which will then be displayed in client applications instead of it.

Have nice nights.
Stas Mishchenkov.

--- "��⮬" - ���⥫쭠� �ଠ "�������".
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi Stas!

14 Oct 20 13:17, you wrote to me:

But while the message is on the TgM servers, it *can* be edited.
The reason why it can't be edited (and I don't expect it to be)
is when the robot grabs it.

You're wrong. A new message of a different type will be created, which will then be displayed in client applications instead of it.

Oh.. so after a TgM message is re-edited, the "different type" contains instructions and other things to the client apps to indicate that it's been re-edited?

I thought that a TgM message would be in a nice and neat pure-text container for your Fidobot to grab. Sounds like there is are a lot of issues to deal with in re-edited messages.


--- GoldED+/W32-MINGW 1.1.5-b20180707
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net)

Hi, August!

14 ��� 20 13:58, August Abolins -> Stas Mishchenkov:

Oh.. so after a TgM message is re-edited, the "different type"
contains instructions and other things to the client apps to indicate
that it's been re-edited?

You don't understand how it works.
I get message-1, then message-2, then message-3, which says it's a new version of message-1. However, message-1 and message-2 have already been sent and there is no way to replace message-1 with message-3.

I thought that a TgM message would be in a nice and neat pure-text container for your Fidobot to grab. Sounds like there is are a lot of issues to deal with in re-edited messages.

Have nice nights.
Stas Mishchenkov.

--- ��������� ���� ������ �����뢠�� ��쪨. ���㦭�� �� ������,�� ⮦� ��ࠢ�
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)