Subj : Re: FTN to Telegram
To   : August Abolins
From : Wilfred van Velzen
Date : Mon Aug 10 2020 03:23 pm

Hi August,

On 2020-08-10 09:17:00, you wrote to me:

AA>>> I lieu of waiting for the ideal programmer to take up the gauntlet
AA>>> of reaching the smartphone crowd with a new API that can talk to
AA>>> BBSes, maybe a Telegram gateway could work with the ready-made
AA>>> Telegram code.

WvV>> What do you mean? Stass is already running such a gateway, so...?

AA> Yes..  Stas is demonstrating that his gateway works.  He has the magic
AA> sauce to transcode FTN bits with Telegram bits.  But would he share the
AA> sauce so that other sysops can adapt it to their BBSes?

Good question. ;)

AA> The Telegram option is not what I perceived that sysops were looking
AA> for. It sounded like sysops where hoping for app/smartphone interface
AA> that ties directly with their BBS software.

Of course a more specific app could be more atractive.

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.  Each sysop could employ a gateway for the echos they
AA> want to support directly.  Otherwise, the system really just needs
AA> someone like Stas's system to do all the work?

More (redundant) gateways would be better of course, but not stricktly necessary. And it wouldn't matter for the Telegram user, as long as there is 1 working for his favorite echomail area. ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.