Hello, Stas Mishchenkov.
On 9/12/20 8:32 PM you wrote:
It seems the most sense is it identifying messages based on the
user ID, not the message body itself. Much like messages
addressed to me are only flagged "to me" when I see them from the
particular feed that message to me was addressed to.
But here everything is not so simple. However, from the Telegram
side, bots do not see each other's messages and there is simply no
such problem. From Fido, however, a flood wave may well rush into
the group, which will not add to its attractiveness for new users.
I figured that I was oversimplifying somewhat, bad habit I developed from years of being the go between between the developers and users for software at a former job. I had to come up with ways to get the point across on how the program worked to people with minimal computer experience, as well as figure out their issues to explain them to the developers.
It's cool that the bots ignore each other. I suppose that helps to limit dumps to Fido. It's the Fido to Telegram where the issue could arise, causing large backlogs of messages for users on the Group.
As I understand it, this process is meant to be a way for people to access some Fido echoes from their phones, tablets, or such while away from their primary computer. So primarily as a backup system. It's understandable that you wouldn't want a huge glut of messages in such cases. I just wish it had a little bit better layout, but that's likely not possible given the primary intent of Telegram.
Meanwhile, it is quite possible to add @PID kludge to messages
from the gate (which is being done now). This will allow the other
gate to recognize the cousin and not gate back messages from it.
Nice addition.
--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: The Oasis, Houston, Texas, USA (2:240/1120.976)