Subj : FTN to Telegram
To : August Abolins
From : Stas Mishchenkov
Date : Thu Aug 13 2020 11:00 am
Hi, August!
10 ��� 20 09:17, August Abolins -> Wilfred van Velzen:
AA> Yes.. Stas is demonstrating that his gateway works. He has the magic
AA> sauce to transcode FTN bits with Telegram bits.
It's not a magic at all. ;)
AA> But would he share the sauce so that other sysops can adapt it to
AA> their BBSes?
It isn't a frontend for bbs.
And for now the code is so integrated in my node system setup, then can not be transferred to another system without great rewritting. :(
AA> The Telegram option is not what I perceived that sysops were looking
AA> for.
It is not for bbs, it is for echoconferences.
AA> It sounded like sysops where hoping for app/smartphone interface that
AA> ties directly with their BBS software.
I'll try to make it more portable and will share the code. But, half of the gate is code, based on my tosser (I'm using HPT) perl extantion.
AA> But since Telegram provides an app + an api to utilize, a gateway
AA> could be an alternative method to get fidonet echos accessible to the
AA> smartphone user.
Yes. But I doubt it would be a good idea to create multiple exit points for fido conferences into the telegram.
AA> Each sysop could employ a gateway for the echos they want to
AA> support directly.
Not right! Any owner (moderator) of an echo may have decision to gating it to the telegram.
AA> Otherwise, the system really just needs someone
AA> like Stas's system to do all the work?
For now it's right. Any owner of telegram grouop or modertor of echo can contact me for gating.
PS: However, such a gate can be considered as a kind of BBS system and used on different nodes of the Fido network.
