Hi Tommi,

On 2020-10-12 16:02:08, you wrote to me:

@MSGID: 2:460/58 00000354

MSGID looks fine now.

Well, normally you want to base your MSGID on the time, and not use a sequence number. Because if you re-install the application (within 3 years), it will probably restart at 0 again, and you have created duplicate MSGID's...

Bye, Wilfred.

Not only that, but if/when this gate software is used on other systems, it could be a problem when the msgids all resume from 00000001. A better formula might be a combination random hex number+serial hex.

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

Hi August,

On 2020-10-12 17:27:11, you wrote to Wilfred van Velzen:

Well, normally you want to base your MSGID on the time, and not use
a sequence number. Because if you re-install the application (within
3 years), it will probably restart at 0 again, and you have created
duplicate MSGID's...

Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001.

No, because the combination of node number and ID should be unique, not just the ID.

A better formula might be a combination random hex number+serial hex.

No, you can't use a random number, because of the small size of the ID, there is a too high chance you generate an identical ID.

Bye, Wilfred.

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

Hello, August Abolins.
On 10/12/20 5:27 PM you wrote:

Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001. A better formula might be a combination random hex number+serial hex.

From what I understand, each gate would be a unique "user" not sharing Telegram Groups, and having different Fido addresses. By this I am referring to the idea of multiple gates for the same echo. Nor do I necessarily see very much overlap in gate/echo combinations.

As I said in another reply, I don't understand all of the technical aspects, but in this case, I don't really see an issue.

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

Hi Wilfred!
12 Oct 20 16:29, you wrote to me:

Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001.

No, because the combination of node number and ID should be unique,
not just the ID.

Oh ok. Definition of MSGID = node # + serial # ?

I was conditioned to think that the msgid was just the hex part/serial part.

But I *think* that thread mechanisms only work with the hex/serial part.

A better formula might be a combination random hex number+serial
hex.

No, you can't use a random number, because of the small size of the
ID, there is a too high chance you generate an identical ID.

Would FTN break if the hex/serial part was more than 8 hex chars?

Would FTN break if the hex/serial part was extended to include the 24 letters of the alphabet?

Even if the hex/serial part was split to be <rando>:<serial>, there would be plenty of room for uniqueness across FTN.



---
* Origin: ----> Point Of VeleNo BBs (http://www.velenobbs.net) (2:333/808.7)

Hi August.

12 Oct 20 17:27:10, you wrote to Wilfred van Velzen:

Well, normally you want to base your MSGID on the time, and not use a sequence number.
Because if you re-install the application (within 3 years), it will probably restart at 0
again, and you have created duplicate MSGID's...

Bye, Wilfred.

Not only that, but if/when this gate software is used on other systems, it could be a problem
when the msgids all resume from 00000001. A better formula might be a combination random hex
number+serial hex.

The other system is not using the fido address 2:460/58. MSGID is a combination of fido address and 8 char hex string. :)

'Tommi

---
* Origin: 2001:470:1f15:cb0:2:221:0:1 (2:221/0.1)

Hi, August!

12 «¬Γ 20 17:27, August Abolins -> Wilfred van Velzen:

Well, normally you want to base your MSGID on the time, and not use
a
sequence number. Because if you re-install the application (within 3
years), it will probably restart at 0 again, and you have created
duplicate MSGID's...

But at the same time, he should easily turn back to Telegram msg_id.

Have nice nights.
Stas Mishchenkov.

--- åÑ¡Θ¿¡δ αÑó¡πεΓ, »«Γ«¼π τΓ« º¡áεΓ, ¡á τΓ« ß»«ß«í¡δ ªÑ¡Θ¿¡δ.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi August.

12 Oct 20 17:27:10, you wrote to Wilfred van Velzen:

Well, normally you want to base your MSGID on the time, and not use a sequence number.
Because if you re-install the application (within 3 years), it will probably restart at 0
again, and you have created duplicate MSGID's...

Bye, Wilfred.

Not only that, but if/when this gate software is used on other systems, it could be a problem
when the msgids all resume from 00000001. A better formula might be a combination random hex
number+serial hex.

The other system is not using the fido address 2:460/58. MSGID is a combination of fido address and 8 char hex string. :)

'Tommi

---

I hear ya. MSGID is defined as node # and 8-char hex. There is plenty of uniqueness right there. But in the case of a reinstall within 3 years, unless the gate software knows where it left off the last time, the new messages after the reinstall may end up being treated as dupes by other systems?

A random number segment in the 8-char string (even if it was as short as 3 hex chars) would significantly reduce that headache.

(BTW.. this message also serves as test to see if the Subj from your fido message is inherited in my Reply.)

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

Hello, Tommi Koivula.
On 10/12/20 7:18 PM you wrote:

Not only that, but if/when this gate software is used on other
systems, it could be a problem when the msgids all resume from
00000001. A better formula might be a combination random hex
number+serial hex.

The other system is not using the fido address 2:460/58. MSGID is
a combination of fido address and 8 char hex string. :)

I thought that was the case. I think I replied somewhere along the line with an answer along that path.

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

Hi, Charles!

12 «¬Γ 20 09:53, Charles Pierson -> August Abolins:

From what I understand, each gate would be a unique "user" not sharing Telegram Groups, and having different Fido addresses. By this I am referring to the idea of multiple gates for the same echo. Nor do I necessarily see very much overlap in gate/echo combinations.

As I said in another reply, I don't understand all of the technical aspects, but in this case, I don't really see an issue.

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

Have nice nights.
Stas Mishchenkov.

--- èáªñδ⌐ αẠíπσá⌐ ¬á¬ »«ß½Ññ¡¿⌐. Å«Γ«¼π τΓ« «ñ¡áªñδ Γᬠ¿ íπñÑΓ.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Charles!

12 «¬Γ 20 09:53, Charles Pierson -> August Abolins:

From what I understand, each gate would be a unique "user" not sharing Telegram Groups, and having different Fido addresses. By this I am referring to the idea of multiple gates for the same echo. Nor do I necessarily see very much overlap in gate/echo combinations.

As I said in another reply, I don't understand all of the technical aspects, but in this case, I don't really see an issue.

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

Have nice nights.
Stas Mishchenkov.

In that, you are right. As long as the matching group is Private on the TgM side, the messages are not really gated anywhere and just remain on your BBS. So the bot is not really gate in the traditional sense. It's just a facilitator to use Telegram as a reader not unlike someone would prefer to use QWK or a newsreader from an nntp feed.

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

Hello, Stas Mishchenkov.
On 10/12/20 10:25 PM you wrote:

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

The bot, is a program which collects the messages and transfers them between Fido and Telegram, correct?

So would it be like a Mailer/Tosser?

I'm trying to understand the functionality.

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: Houston, TX (2:240/1120.976)

I hear ya. MSGID is defined as node # and 8-char hex. There is plenty of uniqueness right there. But in the case of a reinstall within 3 years, unless the gate software knows where it left off the last time, the new messages after the reinstall may end up being treated as dupes by other systems?

A random number segment in the 8-char string (even if it was as short as 3 hex chars) would significantly reduce that headache.

(BTW.. this message also serves as test to see if the Subj from your fido message is inherited in my Reply.)

I have* *a_ trick. ;)_

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

--subj:CR required, or false positives--
Hello Stas. I'm pretty sure I had added the CR after that post. Maybe the attachment (the photo) tripped the parser somehow?

Ma*y be.* _I need take a _look...

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

Hi, Charles!

12 «¬Γ 20 15:10, Charles Pierson -> Stas Mishchenkov:

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

The bot, is a program which collects the messages and transfers them between Fido and Telegram, correct?

Yes. It's close.

So would it be like a Mailer/Tosser?

Not mailer. It creates fido pakets and can read them from the other system.

I'm trying to understand the functionality.

Gate has its own "technical" Fido address and is subscribed on my node at an echo conference like a normal Fido system. Then it toss the mail and upload to the Telegram servers those messages that correspond to the groups. The same is in the reverse order.

Have nice nights.
Stas Mishchenkov.

--- ìá ¬áΦπ ó ú«½«óÑ σ«α«Φ« íÑúπΓ Γáαá¬á¡δ.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello, Stas Mishchenkov.
On 10/13/20 12:25 AM you wrote:

So would it be like a Mailer/Tosser?

Not mailer. It creates fido pakets and can read them from the
other system.

I'm trying to understand the functionality.

Gate has its own "technical" Fido address and is subscribed on my
node at an echo conference like a normal Fido system. Then it toss
the mail and upload to the Telegram servers those messages that correspond to the groups. The same is in the reverse order.

I see. So it acts more as a node or point system off of yours. Not quite as complicated as I thought, but still complicated enough.

I'm surprised you've done as much as you have in about a year or so?

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

Hi, Charles!

12 «¬Γ 20 17:06, Charles Pierson -> Stas Mishchenkov:

I see. So it acts more as a node or point system off of yours. Not
quite as complicated as I thought, but still complicated enough.

I'm surprised you've done as much as you have in about a year or so?

In fact, quite recently, everything worked very differently. I can say that August pushed me to convert the gate into a tosser when he noticed that in some letters the text after some characters is lost. Since then, no more than two or three weeks have passed.

Have nice nights.
Stas Mishchenkov.

--- üπσáΓ∞ - ¡Ñ óδσ«ñ. ì« óáα¿á¡Γ.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Charles!

12 «¬Γ 20 17:06, Charles Pierson -> Stas Mishchenkov:

I see. So it acts more as a node or point system off of yours. Not quite as complicated as I thought, but still complicated enough.

I'm surprised you've done as much as you have in about a year or so?

In fact, quite recently, everything worked very differently. I can say that August pushed me to convert the gate into a tosser when he noticed that in some letters the text after some characters is lost. Since then, no more than two or three weeks have passed.

Have nice nights.
Stas Mishchenkov.

Indeed. That is quite an achievement.

August does seem to have distinctive ideas. Good one's, but sometimes a bit too complicated to put into action within the perimeter of the program I think.

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