On Wednesday February 10 2021 10:49, you wrote to me:
SM> In any case, I have stirred up the hive enough to understand how this SM> can be abused. For myself, I have already turned off the ability to SM> change the recipient address of the robot's response. The only thing SM> left is to change the name. This is what I use for my needs.
Oh Boy. Now you have a maimed version of @REPLYTO implementation....
Your original question was:
SM> Should the Ping Robot take into account the ^aREPLYTO kludge?
My guess is that your answer now is: "Only a maimed version that ignores the address part but honours the user name part".
MvdV>> So we can forget about e-mail gating in the context of PING MvdV>> robots supportinge @REPLYTO.
SM> Of course, this may be needed in the rare case when a node sysop, SM> being on a business trip, for example, for some unknown reason, wanted SM> to check the performance of his node using such a perverse method. SM> However, I left this option to my ping just in case.
If a sysop wants to keep an eye on his system while on a trip, the more logical solution is to install a point system on his laptop/table/smartfone. That way he is not dependent on a third party network and that way he can even engage in discussion.
Regarding the @REPLYTO kludge... My understanding is that this kludge takes care of translating the user name into the Telegram user idea. On the receiving end that is.
But why bother the Fidonet receiver of the message with the burden of this transalation? Why not let the gate handle it? I am not familiar with the inner workings of the Telegram system, but what I glean is that users are identified by a 9? digit decimal number. So why not let the gate do the translation? The Fidonet end need never know about it.
Conversely, in the case of a ping request originating from a Telegram user, instead of putting the TGUID in de @TGUID and the @REPLYUTO kludge, put the TGUID in the From: field of the message. The ping robot does not care and will put the TGUID in the To: field of the retuning pong. Optionally use the @RealName: kludge for the user's real name. Developers of ping robots need not be bothered with the question if they should support @REPLYTO.
