Hi Charles!
12 Oct 20 15:12, you wrote to Stas Mishchenkov:

It gets messages from the Telegram's group and sends them to Fido
echo...

Exactly. So what August vis asking, a "recall message" like
functionality, I don't think is possible is it?

I'm not suggesting a recall in Telegram. I'm just suggesting that the bot wait a little while before snatching the message from the Telegram servers. While the message still lingers on the server, we can change it. But once the bot grabs it from the servers, then it could be considered "sent".

It would be not unlike saving a message with an editor (GoldED, Jam, Squish, MSG, etc..) and still have the ability to adjust the message before packaging it up to actually send it.

If Stas wants the bot to process the messages from the servers immediately, then that is understood. I'll just have to pay more attention to my typos and exclusions.


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

Hello, August Abolins - Charles Pierson.
On 10/12/20 3:36 PM you wrote:

Hi Charles! 12 Oct 20 15:12, you wrote to Stas Mishchenkov: SM>> It
gets messages from the Telegram's group and sends them to Fido SM>>
echo... CP> Exactly. So what August vis asking, a "recall message"
like CP> functionality, I don't think is possible is it? I'm not
suggesting a recall in Telegram. I'm just suggesting that the bot
wait a little while before snatching the message from the Telegram
servers. While the message still lingers on the server, we can
change it. But once the bot grabs it from the servers, then it could
be considered "sent". It would be not unlike saving a message with
an editor (GoldED, Jam, Squish, MSG, etc..) and still have the
ability to adjust the message before packaging it up to actually
send it.

But this isn't an editor. It's a messaging program. The process is more
like text messages than Fido. Stas's program simply grabs those messages
and does the conversion stuff to go between two different communication technologies.
Like a former manager if mine used to say, it's comparing apples to
Buicks.

It takes a different mindset almost to message from one side or the
other.

Fidonet is what 35 years old or so, and honestly, the basic technology
behind it hasn't changed much in that time.

Messaging Apps are by design meant to be sent instantly. They don't have
nice blocks for subjects or areas to put drafts until you are sure
you're ready to send.


So there really isn't a "server" holding the messages on Telegrams side
in the way you're meaning.

Yes, strictly in Telegram, you could delete a message after you sent it.
But anyone in the group still could have read it before that point.

You simply have to re-read your message prior to sending. I know it
takes me a while sometimes. I'm a horrid typist.

If Stas wants the bot to process the messages from the servers
immediately, then that is understood. I'll just have to pay more
attention to my typos and exclusions. --- GoldED+/W32-MINGW
1.1.5-b20180707 * Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)

--
Best regards!
Posted using Hotdoged on Android

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hi, August!

12 «¬Γ 20 23:36, August Abolins -> Charles Pierson:

I'm not suggesting a recall in Telegram. I'm just suggesting that the
bot wait a little while before snatching the message from the Telegram servers. While the message still lingers on the server, we can change
it. But once the bot grabs it from the servers, then it could be considered "sent".

It doesn't make any sense. After you have pressed the "send" button, your changes will be in another message, moreover, in a message of a different type.

If Stas wants the bot to process the messages from the servers immediately, then that is understood. I'll just have to pay more attention to my typos and exclusions.

This is only way. ;)

Have nice nights.
Stas Mishchenkov.

--- ÉπúáΓ∞ß∩ ¼áΓ«¼ ¡Ñσ«α«Φ«... ì« ¡áºδóáΓ∞ óÑΘ¿ ßó«¿¼¿ ¿¼Ñ¡á¼¿ ¡Ñ«íσ«ñ¿¼«.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)