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.
In this case, the Gatebot has "read" the message and has it cued for tranfer.
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.
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.
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.
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.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 409 |
Nodes: | 16 (2 / 14) |
Uptime: | 58:15:12 |
Calls: | 8,572 |
Calls today: | 2 |
Files: | 13,225 |
Messages: | 5,929,801 |