I just got pushed the echomail area: TG.ENGLISH_FROM_ZERO from 2:203/0.

It contains unreadable characters for me. It might be Russian in UTF-8. But the messages don't contain a CHRS; kludge, so I don't know for sure.

The path line on these are all:
@PATH: 5055/182 5020/1042 221/6 1 203/0

So it might be another telegram fido gateway, not run by Stas...?

--- tg BBS v0.6.2
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)

I just got pushed the echomail area: TG.ENGLISH_FROM_ZERO from 2:203/0.

It contains unreadable characters for me. It might be Russian in UTF-8. But the messages don't contain a CHRS; kludge, so I don't know for sure.

The path line on these are all:
@PATH: 5055/182 5020/1042 221/6 1 203/0

So it might be another telegram fido gateway, not run by Stas...?

Any idea what TG.ENGLISH_FROM_ZERO is all about?

I areafix'd it from Tommi's, but it's not on his nntp servers, so I have to wait for content.

Do you think it's Telegram related? "Tg" does also seem to represent Teleguard, or something like that.


--- tg BBS v0.6.2
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)

Hello, August Abolins.
On 11/25/20 2:51 AM you wrote:

Any idea what TG.ENGLISH_FROM_ZERO is all about? I areafix'd it
from Tommi's, but it's not on his nntp servers, so I have to wait
for content. Do you think it's Telegram related? "Tg" does also
seem to represent Teleguard, or something like that.

We shall soon find out. I areafixed it as well, but it's not rescannable.

--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: Houston, TX (1:153/757.26)

Any idea what TG.ENGLISH_FROM_ZERO is all about?

I areafix'd it from Tommi's, but it's not on his nntp servers, so I have to wait for content.

Do you think it's Telegram related? "Tg" does also seem to represent Teleguard, or something like that.

No I have no clue. I didn't bother putting 1 or 2 messages into google translate. And have since deleted them.


--- tg BBS v0.6.2
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)

Hello Charles!

** On Tuesday 24.11.20 - 18:48, Charles Pierson wrote to August Abolins:

Any idea what TG.ENGLISH_FROM_ZERO is all about? I areafix'd it

We shall soon find out. I areafixed it as well, but it's not rescannable.

There's something coming through now, and as well as via nntp.
But Thunderbird doesn't know how to treat the chars in the
body. It seems to be 8-bit though.

--
../|ug

--- OpenXP 5.0.47
* Origin: Mobile? https://t.me/joinchat/SPBwvE1gkHzEKAkapsHkdQ (2:221/1.58)

I just got pushed the echomail area: TG.ENGLISH_FROM_ZERO from 2:203/0.

It contains unreadable characters for me. It might be Russian in UTF-8. But the messages don't contain a CHRS; kludge, so I don't know for sure.

The path line on these are all:
@PATH: 5055/182 5020/1042 221/6 1 203/0

So it might be another telegram fido gateway, not run by Stas...?

All echo conferences with the TG prefix are one-way broadcasts of Telegram channels in Fido on node 2:5055/182. All are available for subscription on my site (2:460/58). All of them are Russian-speaking. It is allowed to write to them from Fido, but nothing gets into Telegram.
This echo conference, as the name suggests, teaches English. The encoding is cp866. Part of UTF-8 characters are not displayed in it.


--- tg BBS v0.6.2
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)

Hi Group,

On 2020-11-25 17:45:11, you wrote to me:

I just got pushed the echomail area: TG.ENGLISH_FROM_ZERO from
2:203/0.

It contains unreadable characters for me. It might be Russian in
UTF-8. But the messages don't contain a CHRS; kludge, so I don't know
for sure.

The path line on these are all:
@PATH: 5055/182 5020/1042 221/6 1 203/0

So it might be another telegram fido gateway, not run by Stas...?

All echo conferences with the TG prefix are one-way broadcasts of Telegram channels in Fido on node 2:5055/182. All are available for subscription on my site (2:460/58). All of them are Russian-speaking.

So probably not so interesting for the rest of fido...

It is allowed to write to them from Fido, but nothing gets into
Telegram. This echo conference, as the name suggests, teaches English.
The encoding is cp866. Part of UTF-8 characters are not displayed in
it.

Thanks for the info. I see there are a lot of those areas, so for the rest of fido, here are all 51 of them:

TG.AVIADISPATCHER
TG.AVIAINCIDENTS
TG.AVIATION_MODE
TG.BAZA
TG.BBBREAKING
TG.BOILERNAYA
TG.CAPT404
TG.CYBERLENINKA
TG.DAILYENG
TG.DATALEAK
TG.DIGITAL_RIGHT_CENTER
TG.DOGE_CLUB
TG.DOLETALIS
TG.EKBLAW
TG.EMM386
TG.ENGLISH_FROM_ZERO
TG.EVROPA_INSIDE
TG.FLYING_UPSIDE_DOWN
TG.FREQUENT_FLYERS
TG.HI_NEWS_CHAT
TG.JEDY_CHANNEL
TG.JUSTICELEGEND
TG.KARAULNIY
TG.LAWS_SHOWTIME
TG.LUCHKOV
TG.MAYOR_FSB
TG.MOBILE_REVIEW_COM
TG.MYSKU_DISCOUNTS
TG.NEVROTIQUE
TG.NEZYGAR
TG.OPERDRAIN
TG.ORDA_MORDORA
TG.POINT_NEWS
TG.R_CHP
TG.RUMAYDAY
TG.SKOLKOVO_LEAKS
TG.SLYNET_TV
TG.STALINGULAG
TG.TEST
TG.THE_IDIOT
TG.TJOURNAL
TG.USHER_II
TG.V1_RU
TG.VARLAMOV_NEWS
TG.VARLAMOV_RU
TG.VOENVZ
TG.WAR_GONZO
TG.WINGSOFWAR
TG.WOW_ENGLISH
TG.YFC_SCHOOL
TG.ZA_TELECOM


Bye, Wilfred.

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

All echo conferences with the TG prefix are one-way broadcasts of Telegram channels in Fido on node 2:5055/182. All are available for subscription on my site (2:460/58). All of them are Russian-speaking. It is allowed to write to them from Fido, but nothing gets into Telegram.
This echo conference, as the name suggests, teaches English. The encoding is cp866. Part of UTF-8 characters are not displayed in it.

Hi Stas(?)

Are you processing those?

BTW.. I see that you are probably using some kind of anonymous posting method. Except for maybe "announcement" type of posts from you, I miss seeing the "From: YourName" in your your posts.


--- tg BBS v0.6.2
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/58)

Hi, August!

25 ­®ï 20 18:11, August Abolins -> Group:

All echo conferences with the TG prefix are one-way broadcasts of
Telegram
channels in Fido on node 2:5055/182. All are available for subscription on
my site (2:460/58). All of them are Russian-speaking. It is allowed to
write to them from Fido, but nothing gets into Telegram. This echo
conference, as the name suggests, teaches English. The encoding is cp866.
Part of UTF-8 characters are not displayed in it.

Hi Stas(?)

Are you processing those?

Yes. All of them are available for subscription and rescaning on 2:460/58.

BTW.. I see that you are probably using some kind of anonymous
posting method. Except for maybe "announcement" type of posts from
you, I miss seeing the "From: YourName" in your your posts.

This is a new feature of Telegram. I didn't notice it was enabled by default. Now I turned it off and there will be no more anonymous messages. ;)

Have nice nights.
Stas Mishchenkov.

--- “¬­ë¥ ¬ë᫨ ¯à¨å®¤ïâ «¨èì ⮣¤ , ª®£¤  å¥à­ï 㦥 ᤥ« ­ .
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

On 25.11.2020 7:56, August Abolins - Charles Pierson :

Hello Charles!

** On Tuesday 24.11.20 - 18:48, Charles Pierson wrote to August Abolins:

Any idea what TG.ENGLISH_FROM_ZERO is all about? I areafix'd it

We shall soon find out. I areafixed it as well, but it's not rescannable.

Autocreated as a passthru echo.

There's something coming through now, and as well as via nntp.
But Thunderbird doesn't know how to treat the chars in the
body. It seems to be 8-bit though.

CP866 set as default for tg.* and *telegram* here now. So russina
messages without @CHRS looks quite fine now.

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.7) Goanna/20201125 Interlink/52.9.7634
* Origin: nntps://news.fidonet.fi - Lake Ylo - Finland (2:221/6.0)