Maybe
it can wait at :00, :15, :30, and :45 time slots.
Fido's technology does not allow you to somehow control an already
sent message. The gate now works in about the same way as the usual
Fido mail tosser, with the only difference that Telegram servers are
used to store and read messages.
That's what I was thinking. Once you send the message, it's sent.
Fido's technology does not allow you to somehow control analready BR> sent message. The gate now works in about the same way
as the usual BR> Fido mail tosser, with the only difference that
Telegram servers are BR> used to store and read messages.
Understood. 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.
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.
I'll just have to wrap my head around the fact that once I press
Send in TgM, then it is unalterable, unlike using a fido message
editor that provides a chance to adjust a message before actually
tossing it.
Hi Charles! 12 Oct 20 16:14, you wrote to Brother Rabbit: CP> That's
what I was thinking. Once you send the message, it's sent. That
seems to be how Stas wants to treat the final press on the TgM's
SEND. But it's the robot that is doing the ultimate final processing
for delivery, not TgM per se. Even my "send" in email is configured
to just stick the messages in the Outbound folder, and not send. I
need to press the big Send/Receive button for actually delivery to
the servers.
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.
I've always sent email once sent, at least since I've moved from Juno.
The only time I have a cue in my outbox is if their is an issue with
the mail server.
Otherwise, I'm likely to forget and they'll sit there for days.
I have had instances when an email would fail to deliver due to a
server connection problem and then I realize that "I shouldn't
send THAT just yet!" :-) And that has been my opportunity to
re-edit it and park it into Drafts, or delete it.
--- GoldED+/W32-MINGW 1.1.5-b20180707 * Origin: ----> Point Of
VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)
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: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 68 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 10:52:22 |
| Calls: | 956 |
| Calls today: | 2 |
| Files: | 7,955 |
| Messages: | 297,261 |