This can become a problem when the same messages from Fido will appear in the same Telegram group, gated on different nodes with different msgid.
Yes.. I can see a problem if different bots pull and feed with
the same original Telegram group. Maybe there should be some kind
of other-bot-aware mechanism that can be added as a kludge. Do
Telegram messages have something like a msgid?
Yes.. I can see a problem if different bots pull and feed with the
same original Telegram group. Maybe there should be some kind of other-bot-aware mechanism that can be added as a kludge. Do Telegram messages have something like a msgid?
For example, if some replies to this message, it would
only flag as to me when I read it from this address. If
I were on my other point, the message would be there, but
Charles Pierson at the Z2 address isn't the same person
as Charles Pierson at the Z4 address. And neither are the
same person as Charles Pierson on Telegram, who I think
also may be another Z2 address based on the bot's address
in Fido?
This case isn't a problem, no. Except perhaps in the case of either
the bot or the system attached to it going offline. Then it's just a matter of the backlog of messages from both sides coming through when
the down section comes back online.
Maybe until all the unique identifier stuff (^TG_PID, or
^TG_MSGID) can be sorted out, then just have it so that there
is only one gate-bot per group, and each BBS is responsible
for their own group.
As it sits right now, we appear to be members of Stas' BBS
only.
I didn't consider separate groups for separate bots, as
it looks somewhat overcomplicated. I was only considering
a second bot as a backup in the cases where the original
bot or system dropped out for a time.
The gating is probably far from being a shared process with
multiple bots at this time.
But Stas is in a fine position to be the founder of establishing the standard ground-rules and the checks and balances for managing dupes, avoiding loops, coming up with the new terminologies for this thing,
etc.
Of course, I would like to have the reliability of work comparable
to Telegram services, but we must not forget that Fido is an
amateur network and most of the nodes are located on home
computers, the reliability of which is not comparable to the
reliability of data centers. The same goes for software. Of
course, we must strive for high reliability and uninterrupted
operation, but it is not always possible to provide this with
amateur means.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,021 |
Nodes: | 17 (1 / 16) |
Uptime: | 16:41:00 |
Calls: | 503,351 |
Calls today: | 10 |
Files: | 107,292 |
U/L today: |
1 files (2K bytes) |
D/L today: |
63,013 files (4,497M bytes) |
Messages: | 441,719 |