Hello All!

I believe that a way for the future of FIDONET to follow could be a geteway to telegram.
Has no one ever thought about developing it?

Young people use Telegram as we (al least I) used FIDONET, having a gateway could open new opportunities to the movement FIDONET!

What do you think aout it?




Pasquale

--- - ITBNET BBS http://bbs.itbnet.eu
* Origin: Tenta, ritenta che alla fine riesci ! (2:335/370)

Re: FTN to Telegram
By: Pasquale Monti to All on Wed Jul 29 2020 11:32 pm

Hello All!

I believe that a way for the future of FIDONET to follow could be a geteway to telegram.
Has no one ever thought about developing it?

Young people use Telegram as we (al least I) used FIDONET, having a gateway could open new opportuniti
to the movement FIDONET!

What do you think aout it?

Pasquale

I think instant messaging scratches a different itch than FidoNET and othernets do, honestly.

Information in instant messengers is highly volatile. Lots of very short messages flying by at light
speed. Compare that with Fido, which people uses for elaborated responses.

I keep hearing about the migration from traditional media to instant messengers... you'd be surpriseed
how worried web forum users and administrators are. However, they are in the same boat. You can't do in
an instant messenger what you do on a forum, and viceversa.

You may as well try to gateway Fido to IRC :-P

--
gopher://gopher.operationalsecurity.es
--- SBBSecho 3.11-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)

Hi August,

On 2020-08-03 23:33:00, you wrote to me:

Interesting. Maybe the destination is just ONE fido area at the
fellow's BBS, for now.

That doesn't make any sense for a fido to telegram bot...

If there is more than one destination area, how do you direct your
netmail post to a specific one?

If there is, it's not clear...

Nothing. So I didn't do it right, or it's not what we are expecting
it to be... ;0

Yes.. there must be something more to the netmail-to-telegram feature
that we are not aware of.

How would you be notified of a reply to your post? Maybe you have to
have the fido feed from the host bbs. That makes the most sense.

Maybe... But than you wouldn't need the gateway. Because you already see every message in the echomail area.

It is an interesting experiment not unlike JAMnntp. It bridges
people from different environments.

Experimenting is one of the perks of FidoNet! ;)

Maybe we can get Stas Mishchenkov at 2:460/58 to explain his system for us.

I've already asked him if there is a "%HELP" for the bot, in netmail...

Bye, Wilfred.

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

Hello Wilfred!

** On Tuesday 04.08.20 - 08:52, Wilfred van Velzen wrote to August Abolins:

Experimenting is one of the perks of FidoNet! ;)

Maybe we can get Stas Mishchenkov at 2:460/58 to explain his system for
us.

I've already asked him if there is a "%HELP" for the bot, in netmail...

I am curious to understand what "the Next FTN generation" means.



There's another fidonet presence here: https://telegram.me/fidonet ....with a grand total of 21 members.




../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi August,

On 2020-08-06 21:07:00, you wrote to me:

Maybe we can get Stas Mishchenkov at 2:460/58 to explain his system
for us.

I've already asked him if there is a "%HELP" for the bot, in
netmail...

He explained a bit. The bot is a gate between a couple of Fidonet echomail areas and corresponding Telegram groups. It's not clear to me what the netmail interface of the bot does, it's not a gateway as far as I understand.

I am curious to understand what "the Next FTN generation" means.

You will have to ask him yourself. ;)

There's another fidonet presence here: https://telegram.me/fidonet ....with a grand total of 21 members.

It's seems to be occupied by a subset of (mostly) Russians, that are also in the https://t.me/fidonet_online Telegram group. Language is also Russian, but it seems to be less active than the other group...

Bye, Wilfred.

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

Hi, Pasquale!

29 �� 20 23:32, Pasquale Monti -> All:

I believe that a way for the future of FIDONET to follow could be a geteway to telegram. Has no one ever thought about developing it?

Young people use Telegram as we (al least I) used FIDONET, having a gateway could open new opportunities to the movement FIDONET!

What do you think aout it?

Such a gate already exists and works. However, the moderators of Fido echo conferences are reluctant to give permission for gating in telegram.

Have nice nights.
Stas Mishchenkov.

--- ��������� ���� ������ �����뢠�� ��쪨. ���㦭�� �� ������,�� ⮦� ��ࠢ�
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, August!

03 ��� 20 23:33, August Abolins -> Wilfred van Velzen:

Interesting. Maybe the destination is just ONE fido area at the
fellow's BBS, for now.

That doesn't make any sense for a fido to telegram bot...

If there is more than one destination area, how do you direct your netmail post to a specific one?

For now netmail is restricted. But it can be translated too.

Experimenting is one of the perks of FidoNet! ;)

Maybe we can get Stas Mishchenkov at 2:460/58 to explain his system for us.

Yes. You can. ;)

There are fido echo areas and Telegram groups with names equal fido echo tags. When a message appears in the Telegram group, it is copied to the echo conference of the same name and vice versa, messages from the echo conference are copied to the same group. The files will be sent as URLs to the Fido part and UUE from Fido will be decoded and sent as files to the telegram.

Have nice nights.
Stas Mishchenkov.

--- ����� � �� - � ���� � ���. ����� � ��� - � ��ࠧ�� ����㭨�����쭥�.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Wilfred!

04 ��� 20 08:52, Wilfred van Velzen -> August Abolins:

Maybe we can get Stas Mishchenkov at 2:460/58 to explain his system
for
us.

I've already asked him if there is a "%HELP" for the bot, in netmail...

And what did he say? ;)

Have nice nights.
Stas Mishchenkov.

--- �������, � �� ��������, �� �� ���� ���� 㧭����.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Wilfred!

** On Friday 07.08.20 - 08:27, Wilfred van Velzen wrote to August Abolins:

I am curious to understand what "the Next FTN generation" means.

You will have to ask him yourself. ;)

I have! But it seems that we may have the wrong guy w.r.t the Telegram destination that used that slogan

Stay tuned. Stas has indicated interest to drop by and explain things.

It sounds like he has identified a need to link traditional Telegram users (mobile, and far from his local region) with dialup users to echos on his bbs.

It doesn't sound too far from the smartphone user-base scenario that has
been discussed here. Telegram already provides the API and the iOS/
Android apps, and Stas has learned to leverage it to work with echomail.

There's another fidonet presence here: https://telegram.me/fidonet
....with a grand total of 21 members.

It's seems to be occupied by a subset of (mostly) Russians, that are
also in the https://t.me/fidonet_online Telegram group. Language is also Russian, but it seems to be less active than the other group...

Some of the aspects of Telegram are intriguing: privacy within a group, unsending (deleting messages), voice chat, message search, msg tracing/ threading, file sharing, end-to-end encryption, secret chats, ..to name a few.

For "echomail" all the secret stuff is nullified, but bridging mobile
users to bbs users seems to be the main purpose.


../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi, Wilfred!

07 ��� 20 08:27, Wilfred van Velzen -> August Abolins:

It's seems to be occupied by a subset of (mostly) Russians, that are
also
in the https://t.me/fidonet_online Telegram group. Language is also Russian, but it seems to be less active than the other group...

There are a lot of English-speaking users

Have nice nights.
Stas Mishchenkov.

--- - � �� �� ��樮���쭮��...? - ����-��. � ��? - ���. - � � ⠪?
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, August!

09 ��� 20 10:37, August Abolins -> Wilfred van Velzen:

I am curious to understand what "the Next FTN generation" means.

You will have to ask him yourself. ;)

I have! But it seems that we may have the wrong guy w.r.t the Telegram destination that used that slogan

In general, in the Russian-speaking part of Fido, this is rather a kind of good teasing on young programmers who are going to write a "new Fidonet", and not a slogan.

Stay tuned. Stas has indicated interest to drop by and explain
things.

I'll try. ;)

It sounds like he has identified a need to link traditional Telegram
users
(mobile, and far from his local region) with dialup users to echos on his bbs.

Not "need". It's a hobby, not more.

Some of the aspects of Telegram are intriguing: privacy within a
group, unsending (deleting messages), voice chat, message search, msg tracing/threading, file sharing, end-to-end encryption, secret chats,
..to name a few.

For "echomail" all the secret stuff is nullified, but bridging mobile users to bbs users seems to be the main purpose.

Not quite right, but something like this.

The choice in favor of Telegram was made because it provides a free opportunity to do all this.

Have nice nights.
Stas Mishchenkov.

--- �᫨ ����� �� �⮨� � ᬥ⠭�, �祢����, ������� �� �����!
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Answering a msg from Stas Mishchenkov:

Hi, August!

09 ��� 20 10:37, August Abolins -> Wilfred van Velzen:

For "echomail" all the secret stuff is nullified, but bridging mobile users to bbs users seems to be the main purpose.

I can create private groups for personal use. This gives me the ability to read and write to Fido Echoconferencing using telegrams.

Have nice nights.
Stas Mishchenkov.

Unfortunately from the Telegram side this creates a terrible over-quoting.
--- tg2fido.pl
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

Hi, All!

10 ��� 20 13:40, Brother Rabbit -> Stas Mishchenkov:

Unfortunately from the Telegram side this creates a terrible
over-quoting.

This is how it looks from the telegram side. https://brorabbit.g0x.ru/files/2020-08-10_13-43-06.png

Have nice nights.
Stas Mishchenkov.

--- ���� �ਧ����� ��㯮�� ���� ������ ������⢨� ��뤠. �.�३�.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi August,

On 2020-08-09 11:27:00, you wrote to me:

Is Telegram the only techology that offers a free API/protocol/schema
for this sort of thing?

I haven't looked into it, but my guess is that most of them offer some kind of api for automated messages...

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

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

Bye, Wilfred.

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

Hello Wilfred!

** On Monday 10.08.20 - 13:35, Wilfred van Velzen wrote to August Abolins:

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

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

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

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

But since Telegram provides an app + an api to utilize, a gateway could be
an alternative method to get fidonet echos accessible to the smartphone
user. Each sysop could employ a gateway for the echos they want to
support directly. Otherwise, the system really just needs someone like Stas's system to do all the work?

--
../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi August,

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

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

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

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

Good question. ;)

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

Of course a more specific app could be more atractive.

But since Telegram provides an app + an api to utilize, a gateway
could be an alternative method to get fidonet echos accessible to the smartphone user. Each sysop could employ a gateway for the echos they want to support directly. Otherwise, the system really just needs
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)

Hi, August!

10 ��� 20 09:17, August Abolins -> Wilfred van Velzen:

Yes.. Stas is demonstrating that his gateway works. He has the magic sauce to transcode FTN bits with Telegram bits.

It's not a magic at all. ;)

But would he share the sauce so that other sysops can adapt it to
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. :(

The Telegram option is not what I perceived that sysops were looking
for.

It is not for bbs, it is for echoconferences.

It sounded like sysops where hoping for app/smartphone interface that
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.

But since Telegram provides an app + an api to utilize, a gateway
could be an alternative method to get fidonet echos accessible to the smartphone user.

Yes. But I doubt it would be a good idea to create multiple exit points for fido conferences into the telegram.

Each sysop could employ a gateway for the echos they want to
support directly.

Not right! Any owner (moderator) of an echo may have decision to gating it to the telegram.

Otherwise, the system really just needs someone
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.

Have nice nights.
Stas Mishchenkov.

--- �� ���� � ������ ��� ����� �ࠪ���.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, August!

09 ��� 20 10:37, August Abolins -> Wilfred van Velzen:

For "echomail" all the secret stuff is nullified, but bridging mobile users to bbs users seems to be the main purpose.

I can create private groups for personal use. This gives me the ability to read and write to Fido Echoconferencing using telegrams.

Have nice nights.
Stas Mishchenkov.

--- Second try
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Wilfred!

13 ��� 20 14:10, Wilfred van Velzen -> Stas Mishchenkov:

He said: not yet. ;-)

In fact, it is not difficult to make a netmail gate in telegrams and vice versa. However, in order to write from Fido to Telegram, you need to know the UserID in Telegram. Now every letter from Telegram to Fido has a kludge @TGUSERID, which will allow to write a private message from Fido to this user.

Have nice nights.
Stas Mishchenkov.

--- ��� ��ᯮ����� ��-���� �������, � � ⠪ �� ᮡ����� ��祣� ������.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Stas!

Glad you could join us in FUTURE4FIDO! :)


** On Thursday 13.08.20 - 10:58, Stas Mishchenkov wrote to August Abolins:

There are fido echo areas and Telegram groups with names equal fido
echo tags. When a message appears in the Telegram group, it is copied
to the echo conference of the same name and vice versa, messages from
the echo conference are copied to the same group.

How much use is the Telegram/echomail gate getting?

How many participants are there?

How many different echos are you processing?

The files will be sent as URLs to the Fido part and UUE from Fido
will be decoded and sent as files to the telegram.

I'm pressed that you are also servicing movement of files. With the URLs
to the Fido part, does the user pull the file off a Telegram server?

I have many other questions, but I'll try to control myself - I promise.


--
../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi, August!

13 ��� 20 21:47, August Abolins -> Stas Mishchenkov:

How much use is the Telegram/echomail gate getting?

I don't quite understand what you mean.

How many participants are there?

About 120.

How many different echos are you processing?

There is three groups of Telegram available publicly, any Telegram user can join. Several echoes is gated for my personal use only.

The files will be sent as URLs to the Fido part and UUE from Fido
will be decoded and sent as files to the telegram.

I'm pressed that you are also servicing movement of files.

May be "impressed"? ;)

With the URLs to the Fido part, does the user pull the file off a Telegram server?

No. I hold files on my own server.

I have many other questions, but I'll try to control myself - I
promise.

Feel free to ask me.

Have nice nights.
Stas Mishchenkov.

--- ��뤭� �뢠�� ⮫쪮 �� �, �� �������. ��������.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Wilfred!

10 Aug 20 15:23, you wrote to August Abolins:

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

Good question. ;)

Telegram bots are implemented in such a way that they do not see messages from each other. Thus, the presence of two different gates in the same echo conference will lead to the loss of some of the discussion threads for Fido part.

Stas


--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Default GoldED Origin <---- (2:460/58)

Hello August!

15 Aug 20 23:03, you wrote to me:

How much use is the Telegram/echomail gate getting?

I don't quite understand what you mean.

I meant, how much activity do you measure through the gateway?

About three hundred messages per day, excluding mine.

How many participants are there?

About 120.

I see 100 in fidonet.online now. Are you including additional users
in the FidoNet(unofficial) group too?

OR.. is it just the two groups that the user Fido2telebot is a member
of? I see Fido2telebot in the PVT.ZONA and fidonet.online groups.

fidonet.online, PVT.ZONA, FidoNet.unoficial -------------------------------------^

How many different echos are you processing?

There is three groups of Telegram available publicly, any
Telegram user can join. Several echoes is gated for my personal
use only.

Would you be inclined to expand the concept to an english-speaking
crowd?

Why not?

I've seen some Fido2telebot posts. I see that you maintain the full
name of the user coming in from the Fido side. Are you able to
maintain threading with replies in the Telegram-to-Fido direction?

When a bot reads a message from a telegram, it still cannot know what @MSGID it will have in Fido. So replay tree can not be made for now.

Feel free to ask me.

I've already started; see above. :)

You are welcome.

Now that I am in Telegram and looking around, I see that it's not a
bad system at all. The S)earch feature is awesome.

Try my Fidogle on 2:460/58. ;)

From : August Abolins 2:221/1.58
To : Fidogle 2:460/58
Subj : %Help

The support for
attaching files and photos and having them actually in their own
"albums" or section for a discussion group is pretty good.

Some kind of this is in Fido too. Look at https://brorabbit.g0x.ru/uue/

I think you already mentioned that when your gateway processes a
Telegram message that includes an image, the fido echo user sees a
link for it from your own server?

Yes.

Stas


--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Default GoldED Origin <---- (2:460/58)

Hi, August!

15 ��� 20 23:33, August Abolins -> Stas Mishchenkov:

From a moderator's perspective, Telegram seems to have excellent
controls available.

It would be nice if the moderator agreed to moderate telegram users as well. Usually, this is the problem of the gatemaster.

Have nice nights.
Stas Mishchenkov.

--- �祭� �������� �������� � ��� ��� � ����.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Stas!

** On Sunday 16.08.20 - 14:15, Stas Mishchenkov wrote to August Abolins:

Try my Fidogle on 2:460/58. ;)

From : August Abolins 2:221/1.58
To : Fidogle 2:460/58
Subj : %Help

I tried to send direct/crash. It would not negotiate. What are you using
for the frontend? My OpenXP only has a known problem with mbcico systems.




--
../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi, Ogg!

17 ��� 20 19:07, Ogg Abo -> Stas Mishchenkov:

I am replying via TG, just to see what this looks like. Meanwhile,
thanks for the update on the server connections.

It looks like ugly owerquoting, but it works.

Have nice nights.
Stas Mishchenkov.

--- ��뤭� �뢠�� ⮫쪮 �� �, �� �������. ��������.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Stas!

** On Monday 17.08.20 - 18:48, Stas Mishchenkov wrote..

I understand this to mean that you would be fine with
just the gating operation, and not the moderation task
(spotting spam, blocking users, etc) on the Telegram
side?

Yes. You are right.

Maybe a handful of other echos could open up for the gate.
The current moderator just needs to create matching-name
private group on Telegram and your Fido2telebot personality
just "joins" it?

The moderator can always contact me to block the user
from the gate.

It is good to have your willingness to step in. Thanks.

As a minimum, I would assume that for fidonet
purposes, any gated group would be best set up as a
private group to start with?

In deed. However, open groups are very useful and bring
new users to the Fido network, as well as help old ones
to return.

Hmmmm.. maybe this new outreach of fidonet echos could use
a dedicated Telenet-only FIDONET.STARTHERE (or something
like that) group or a read-only channel that advertises
which echos are gated and promotes this smooth and easy
accessibility via smartphone.

BTW.. how long have you been gating Telegram|FTN ?

What? �|8-( )=

And that is secret glyph/code for what? :/

--
../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hello Stas!

** On Sunday 16.08.20 - 14:15, Stas Mishchenkov wrote to August Abolins:

When a bot reads a message from a telegram, it still
cannot know what @MSGID it will have in Fido. So replay
tree can not be made for now.

What does the message "header" look like in Telegram? Isn't
there a unique ID for each post and a trace to a reply? I
am thinking that it wouldn't be too much different than the
msg references in nntp headers.

Now that I am in Telegram and looking around, I see
that it's not a bad system at all. The S)earch
feature is awesome.

Try my Fidogle on 2:460/58. ;)

THAT is precisely what I was asking about months ago (but
had wondered about for years) for an equivalent to the
existing FILEFIND systems but for echomail messages. I am
glad someone was thinking of such a thing too. It works
rather well. How far back do you keep old messages?


--
../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi, August!

18 ��� 20 21:15, August Abolins -> Stas Mishchenkov:

Maybe a handful of other echos could open up for the gate.

This requires the consent of the moderator.

The current moderator just needs to create matching-name
private group on Telegram and your Fido2telebot personality
just "joins" it?

Right. The moderator can create a group in Telegram himself and add a bot there. After that contact me to add this echo conference to the list of gated ones.

Hmmmm.. maybe this new outreach of fidonet echos could use
a dedicated Telenet-only FIDONET.STARTHERE (or something
like that) group

It is quite logical to create a Telegram group for new users, gated in Fido. However, such a group lacks a full understanding of what the Fido network is and what a membership in it would actually look like.

or a read-only channel that advertises
which echos are gated and promotes this smooth and easy
accessibility via smartphone.

I think such a channel is quite possible to create, but it will not need to be gated in Fido.

BTW.. how long have you been gating Telegram|FTN ?

I do not remember exactly. A little over a year or so.

What? �|8-( )=

And that is secret glyph/code for what? :/

This emoticon depicts a face with a mouth wide open in surprise, eyes wide open in surprise, hair standing on end and a beard. ;)

Have nice nights.
Stas Mishchenkov.

--- "��⮬" - ���⥫쭠� �ଠ "�������".
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, August!

18 ��� 20 21:48, August Abolins -> Stas Mishchenkov:

What does the message "header" look like in Telegram?

A message in a telegram is a tree-like object in which there is quite a lot of information, not all of it is currently used by the gate.

Isn't there a unique ID for each post and a trace to a reply?

Yes.

I am thinking that it wouldn't be too much different than the
msg references in nntp headers.

Probably yes.

Now that I am in Telegram and looking around, I see
that it's not a bad system at all. The S)earch
feature is awesome.

Try my Fidogle on 2:460/58. ;)

THAT is precisely what I was asking about months ago (but
had wondered about for years) for an equivalent to the
existing FILEFIND systems but for echomail messages.

Moreover, it works in such a way that you can also find a file by name or even part of the description. This is due to the fact that echoes with announcements of file echo processors are also viewed.

I am glad someone was thinking of such a thing too. It works
rather well.

Glad it might be helpful.

How far back do you keep old messages?

In fact, my base is not very old, only two or three years, but most of the echoes do not purge at all.

Have nice nights.
Stas Mishchenkov.

--- �� 堫�� �� ⮫쪮 ���� ᫠���, �� � ᢨ���� ���⭠, 堫�쭠 � ���ୠ.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, August!

20 ��� 20 00:42, Stas Mishchenkov -> August Abolins:

Moreover, it works in such a way that you can also find a file by
name or
even part of the description. This is due to the fact that echoes with
announcements of file echo processors are also viewed.

Try

Subj: %Search

%Words The First FIDONET NODELIST

I'm sorry. I had no idea that the answer could be so huge. Apparently, it was necessary to clarify the request.

%Words the first fidonet nodelist Area FILE.* bytes

It will find five messages.

Have nice nights.
Stas Mishchenkov.

--- ��e�, �e�e����� �e� � ����ய���, ���� ��o���� �� ��� �� �e� � �o⫥
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Stas!

** On Friday 21.08.20 - 09:00, Stas Mishchenkov wrote to August Abolins:

Try

Subj: %Search

%Words The First FIDONET NODELIST

I'm sorry. I had no idea that the answer could be so huge. Apparently, it was necessary to clarify the request.

Heheheh! No problem. At first I thought this was a trap and I
fell for it. <g> But after I sent it, I realized that this was
going to search through a whole slew of echo areas.

%Words the first fidonet nodelist Area FILE.* bytes

I can see that being a much narrow hit list.

BTW.. the messages arrive with no char kludge, hence Jamnntp and
neither my OpenXP seems to know how to interpret the 8-bit chars.


--
../|ug

--- OpenXP 5.0.45
* Origin: The future is not what it used to be. (2:221/1.58)

Hi, August!

23 ��� 20 12:58, August Abolins -> Stas Mishchenkov:

BTW.. the messages arrive with no char kludge, hence Jamnntp and
neither my OpenXP seems to know how to interpret the 8-bit chars.

Thank. This is a helpful note. I didn't notice there was no kludge. I will fix it.

Have nice nights.
Stas Mishchenkov.

--- ������ - �� ����� ������ ��쪨 � �ᯮ�������, �� ���� ������ �㯨��
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)