Subj : Can I ask, is the bot software available for me to test out here? To : John Dovey From : August Abolins Date : Thu May 06 2021 18:22:00 Hello John Dovey! ** On Friday 07.05.21 - 00:28, John Dovey wrote to August Abolins: JD> Let me see if I understand this correctly. The TGUID is an JD> automated user created on the BBS hosting the robot? Stas would clearly be the best person to answer.. hope he jumps in. But I *do* know that the TGUID is actually the id that the Telegram system creates to identify you. Stat's bot simply leverages it to help redirect incoming netmail to the correct Telegram user. JD> So, in theory, If the concept of the robot was taken JD> further, then each BBS could implement the gateway, and JD> have their local BBS user ID <-linked -> Telegram number, JD> so addresses could be figured out programmaticly at the BBS JD> and gated accordingly. That sounds about right, I think. JD> The way it is now, this is running on a test basis, so we JD> have to use the bot (%userinfo) to register our information JD> which essentially creates a new user account on 2:460/256? No. Stas implemented the "register" process to steer people to the features of %userprofile (ie, %help, %list, etc). Once a user talks to @Fido2telegram bot and optionally designs a signature, a welcome message, etc, the bridge from Telegram-to- Fido opens. JD> With a roll out of the gateway software, I would install it JD> so that my users would be able to get gated telegram JD> messages at @4:920/1 ? Are you referring to netmail? The @4:920/1 would be something your gateway software implementation would use to steer any netmail to the correct Telegram user. Otherwise, the tguid is probably not used when Telegram users have simply "joined" the group that is linked with an echo. JD> Does that about describe it? Perhaps Stas (@BroRabbit) can correct me if necessary and elaborate on anything else. -- ../|ug --- OpenXP 5.0.49 * Origin: tg_bbs-> https://t.me/joinchat/TWCQfOZqwwOmweR1 (2:221/1.58) .