Subj : Telegram and JavaScript
To   : echicken
From : John Dovey
Date : Fri Apr 22 2022 17:41:07


 e> Ah, bots. I thought you were talking about something completely different.
 e> (I'm not sure what "run/launch a JavaScript app directly from the client"
 e> means here; bots typically run standalone / implement the client
 e> themselves.)

Yes, sorry. My sausage fingers typed bit instead of not.


 JD>> Off the top of my head, a few of the things that might fit with a bot
 JD>> integration might be - access to file areas
 JD>> - download of mail (like a QWK door)
 JD>> - a binkp like transfer of mail packets 
 JD>> etc

 e> Using a bot as a mailer seems a bit janky to me, but I'm probably missing
 e> something. We've already got systems in place for moving packets around. Is
 e> the goal to use Telegram's network for mail transfers, eg. my bot exchanges
 e> mail with your bot, with each BBS/node running its own bot?

That's what I was thinking.
https://core.telegram.org/bots/webapps
This is probably a better url than the one I shared before.
I was thinking that just like the web interface allows access to the BBS using a web browser, it might be possible to do the same using the Telegram client 

This would do a number of things.
Broaden the access (especially on mobile) to BB systems (especially on mobile) by making it possible on the devices and in the format that the modern users would find familiar.
The app is already installed on millions of devices and being used, so this would then just be one more "contact" for them that happened to be a BBS. 
The Bot talks to "clients" by polling Telegram servers, so it should be possible for an SBBS installation to have a local bot to which many users could connect. The bot would simply provide an interface to services tbe BBS provides (echos, Netmail, file areas etc). 
One of the interesting things is that it would get around the problem I'm having with ENat... so more people could run it without having issues of people not being able to connect (telnet etc) to their boards 
This same advantage would apply to a binkp type bit which would also make the system accessible even behind a NAT or firewall.

JD
--- AfterShock/Android 1.6.8
 * Origin: Firecat Mobile (4:920/69.1)

.