It would be great if someone did a tutorial on how to create the tgm
<-> ftn Gateway for Fidonet and other areas of FTN networks.
Quoting Charles Pierson to Mauro Veiga <=-
Hello, Mauro Veiga : AUGUST ABOLINS.
On 10/30/20 8:43 AM you wrote:
It would be great if someone did a tutorial on how to create the tgm
<-> ftn Gateway for Fidonet and other areas of FTN networks.
I'm sure that once Stas has it in a manner ready to release, it will
have such documentation as needed.
Currently, the Gateway runs through Stas's system, and links to echos
that he is connected to as the interest in such echos is learned
about, as long as the moderator of the echo is OK with it.
Okay. I wait for Stas make the tutorial. There are areas
that he doesn't echo and other FTN networks that could
benefit from it.
On 01/11/2020 5:54 a.m., Charles Pierson : August Abolins wrote:
.. it may or may not be possible in DOS.
I did say that I thought there were some restrictions. I'mWhen Stas releases his work, it ought to be an interesting study
thinking even if the particular functions that aren't available
are used in Stas's bot, there could be a work around for them.
between code and API. Reverse-engineering heaven!
Quoting August Abolins to Mauro Veiga <=-
On 01/11/2020 9:53 a.m., Mauro Veiga : AUGUST ABOLINS wrote:
Okay. I wait for Stas make the tutorial. There are areas
that he doesn't echo and other FTN networks that could
benefit from it.
[snip]
Currently, we are looking to open the gate for echos that can
accommodate free-flow paragraphs. Anything with a fixed-width
line-length looks a bit jagged on the Telegram side.
I read FUTURE4FIDO. Thanks.
Try to read some of his earlier posts. He mentions that there won't
be any step-by-step guide. It will require some coding prowess to
adapt the gate to match your own particular configuration.
The code is in perl. Thus, a *nix system would be required.
Try to read some of his earlier posts. He mentions that there won't
be any step-by-step guide.
It will require some coding prowess to
adapt the gate to match your own particular configuration.
The code is in perl. Thus, a *nix system would be required.
Depending on the functions that the tg2fido perl uses:
--[begin citation]--
Perl under DOS lacks some features of perl under UNIX because of deficiencies
in the UNIX-emulation, most notably:
[o] fork() and pipe()
[o] some features of the UNIX filesystem regarding link count and
file dates
[o] in-place operation is a little bit broken with short filenames sockets
Hi, August!
01 ноя 20 18:13, August Abolins -> Mauro Veiga:
Try to read some of his earlier posts. He mentions that there won't
be any step-by-step guide.
Yes. Will not be. This will reduce the likelihood of hooliganism and will only allow those who understand what they are doing to use this program.
It will require some coding prowess to
adapt the gate to match your own particular configuration.
This is not necessary now. The program has its own configuration files, which even contain short descriptions, and command line switches. In addition, it is no longer tied to a specific tosser and processes the PKT itself.
The code is in perl. Thus, a *nix system would be required.
Not necessary. http://strawberryperl.com/
Have nice nights.
Stas Mishchenkov.
Yes. Will not be. This will reduce the likelihood of hooliganism
and will only allow those who understand what they are doing to
use this program.
That makes sense, I guess. In theory, someone could abuse it and spam echoes I
suppose.
This is not necessary now. The program has its own configuration
files, which even contain short descriptions, and command line
switches. In addition, it is no longer tied to a specific tosser
and processes the PKT itself.
Both ways? To and from Fido?
The code is in perl. Thus, a *nix system would be required.
Not necessary. http://strawberryperl.com/
Ahh, perhaps a better version than one I looked at.
| Sysop: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 143:31:52 |
| Calls: | 166 |
| Files: | 5,389 |
| Messages: | 223,276 |