Hello, Stas Mishchenkov.
On 9/29/20 9:00 AM you wrote:

The part sending messages from Fido has been completely rewritten.
Now I am watching and testing. In the meantime, I am radically
rewriting a part from Telegram to Fido. There, unfortunately, not everything is so simple. There will be new opportunities in this
part.

I have noticed something different with your reply here.

I posted my message in Telegram.
Ordinarily, my NNTP feed would flag your reply as to me, but my Points wouldn't. However, all 3 currently do. I have a new Webpoint address I haven't entirely set up yet, but I suspect it would as well.

PS: After small rasp processing, the gate can be used instead of
the tosser. ;) Have nice nights.
Stas Mishchenkov.
--- ������ - �� ����� �� ��� ���������, �� 㦥 �� ����砥����.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: Android device, Milky Way (2:240/1120.976)

Hi, Charles!

29 ᥭ 20 08:20, Charles Pierson -> Stas Mishchenkov:

I have noticed something different with your reply here.

I posted my message in Telegram.

Why do you think so?

= FUTURE4FIDO (2:460/5858) ====================================================
Msg : 769 of 771 Rcv
From : Charles Pierson 4:902/26.52 Mon 28 Sep 20 17:54
To : Stas Mishchenkov
Subj : Anything New? =============================================================================== @MSGID: 4:902/26.52 87ddb337
@PID: Hotdoged/2.13.5/Android
@TID: jNode/Android
@CHRS: CP866 2
Hello, Stas,

Anything new on the development front?

...

--
Best regards!
Posted using Hotdoged on Android
-+- Hotdoged/2.13.5/Android
+ Origin: Android device, Milky Way (4:902/26.52)
SEEN+BY: 460/58 777 1124 5858 467/888 5054/30
@PATH: 902/26 90/1 229/426 317/3 770/1 712/848 640/1384 460/58 ===============================================================================

Ordinarily, my NNTP feed would flag your reply as to me, but my
Points wouldn't. However, all 3 currently do. I have a new Webpoint address I haven't entirely set up yet, but I suspect it would as well.

Nothing is clear, but very interesting. ;)

Have nice nights.
Stas Mishchenkov.

--- ����� ࠧ ��堩 ��� ��᫥����. ��⮬� �� ������� ⠪ � �㤥�.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Charles!

28 ᥭ 20 17:54, Charles Pierson -> Stas Mishchenkov:

Anything new on the development front?

Slightly changed the appearance of messages from Fido to Telegram. ;)

Have nice nights.
Stas Mishchenkov.

--- ���᫠ ���窠 �窮 ��ਪ� � ��ࠧ�⥫쭮 ��ᬮ�५� �� �������.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Answering a msg from Stas Mishchenkov:

Hi, Charles!

28 ᥭ 20 17:54, Charles Pierson -> Stas Mishchenkov:

Anything new on the development front?

Slightly changed the appearance of messages from Fido to Telegram. ;)

Have nice nights.
Stas Mishchenkov.

Looks good!

A suggestion for future consideration:

With smartphone texting in mind, how about allowing for a shorter two-char version for --Subj: when composing a message ?

--Subj: or --Sb: or --sb:

And then as you may come up with other --Header: tags, provide a two-char version that would work too.


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

Hi, August!

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

Anything new on the development front?

Slightly changed the appearance of messages from Fido to Telegram. ;)

Looks good!

A suggestion for future consideration:

With smartphone texting in mind, how about allowing for a shorter two-char version for --Subj: when composing a message ?

--Subj: or --Sb: or --sb:

I will consider this proposal. It was originally designed as a purely technical label. It seems to me that such a simplification can lead to false positives of recognition.

And then as you may come up with other --Header: tags, provide a
two-char version that would work too.

Have nice nights.
Stas Mishchenkov.

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

On 02/10/2020 12:00 a.m., Stas Mishchenkov : August Abolins wrote:

A suggestion for future consideration:

With smartphone texting in mind, how about allowing for a
shorter two-char version for -- Subj: when composing a
message?

--Subj: or --Sb: or --sb:

I failed to include the lowercase --subj: version of the tag to the
above list, for completeness.

I will consider this proposal. It was originally designed
as a purely technical label. It seems to me that such a
simplification can lead to false positives of recognition.

Just to clarify, I was only suggesting the use of the 2-char
versions when *creating* or *writing* a message on the Telegram side.

The full version of --Subj: on incoming messages is fine, and should
probably remain unchained.

WRT false positives, I can appreciate the problem you foresee. If
there are alternatives to a header then it could be just as easy to
mistype --Sb: as --sj: or --su: or something like that.

Therefore, maybe consider a rule for the shorter form to be just the
first 2 letters (since --To: and --to: are like that). That would be
consistent and easier to remember.

.: --Subj: or --subj: or --Su: or --su: ..might be better?


--

--- TB(Stealth)/Win7
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)