By the way, why not?

As far as I know, the permission of the moderator was obtained before this echo conference was connected to Telegram.

Strictly speaking, this is not exactly a gate in Telegram. It looks more like a BBS with access via Telegram.

The term "gate" seems to paint some preconceived ideas. For instance, the term "gated to usenet" emits a notion of uncontrolled public distribution and a pool for spam. "Gate" can have a negative connotation.

Maybe it would be worth finding another term for the Fido<->TgM magic that you created. It is technically just a translation from your system (like a fido boss node or host) to access Telegram and accommodate smartphones and tablets much like what HotdogEd and Aftershock accomplish.

Instead of "--- tg2fido gate v0.6.1", how about "--- tgm/fido portal vn.n.n" as a way to deprogram the tainted mind?

--- tg2fido gate v0.6.1
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

The term "gate" seems to paint some preconceived ideas. For instance, the term "gated to usenet" emits a notion of uncontrolled public distribution and a pool for spam. "Gate" can have a negative connotation.

Maybe it would be worth finding another term for the Fido<->TgM magic that you created. It is technically just a translation from your system (like a fido boss node or host) to access Telegram and accommodate smartphones and tablets much like what HotdogEd and Aftershock accomplish.

Instead of "--- tg2fido gate v0.6.1", how about "--- tgm/fido portal vn.n.n" as a way to deprogram the tainted mind?

I think BBS comes closest.

--- tg2fido gate v0.6.1
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

I think BBS comes closest.

Right. You are leveraging the free and open-source Telegram API and its 24/7 servers to provide another "interface" for users to reach *your* BBS.

--- tg2fido gate v0.6.1
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

Right. You are leveraging the free and open-source Telegram API and its 24/7 servers to provide another "interface" for users to reach *your* BBS.

This is exactly what I meant. Free Telegram resources are used to access Fido. The only bad thing is that proprietary resources are used to store messages. However, the vast majority of echo conferencing has been indexed and cached by Google, I think this is not a big problem at all.

--- tg2fido gate v0.6.1
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

This is exactly what I meant. Free Telegram resources are used to access Fido.
The only bad thing is that proprietary resources are used to store messages. However, the vast majority of echo conferencing has been indexed and cached by Google, I think this is not a big problem at all.

Many fido echos have been available to read by the anonymous public for many years on Synchronet sites such as https://sestar.synchro.net/msgs/index.ssjs and https://freeway.apana.org.au/msgs/index.ssjs and even archivers such as https://www.ipingthereforeiam.com/bbs/msgs/

The messages at all of those are most certainly passed through the grips of Google.

However, if a BBS hosted an echo exclusively on its own system and made it available on Telegram as an alternative way to read them (via private groups), then the system would actually be more exclusive and private (completely out of Google's reach) than the usual way fidonet is moving around now. However, if someone were to use the webapp version of Telegram, I suppose there would be exposure to the data no different from the other web solutions to read echomail.

I never thought of messages stored on Telegram servers as a bad thing. It's not much different than a BBS using a VPS to operate and process messages.

You are simply leveraging Telegram servers as a kind of VPS to reach out to smartphone/tablet users.

--- tg2fido gate v0.6.1
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

Good ${greeting_time}, August!

05 Nov 20 06:55, you wrote to Brother Rabbit:

This is exactly what I meant. Free Telegram resources are used to
access Fido. The only bad thing is that proprietary resources are
used to store messages. However, the vast majority of echo
conferencing has been indexed and cached by Google, I think this
is not a big problem at all.

Many fido echos have been available to read by the anonymous public
for many years on Synchronet sites such as https://sestar.synchro.net/msgs/index.ssjs and https://freeway.apana.org.au/msgs/index.ssjs and even archivers such
as https://www.ipingthereforeiam.com/bbs/msgs/

The messages at all of those are most certainly passed through the
grips of Google.

which is also fucking annoying.

* Origin: kakistocracy (2:280/464.47)