1. Forum
  2. FidoNet
  3. FUTURE4FIDO

  • msgid, 3 years

    From August Abolins@2:460/58 to Wilfred van Velzen on Mon Oct 12 17:27:10 2020
    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)
  • From August Abolins@2:333/808.7 to Wilfred van Velzen on Mon Oct 12 17:01:48 2020
    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)
  • From Charles Pierson@2:240/1120.976 to Stas Mishchenkov on Mon Oct 12 15:10:30 2020
    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)
  • From Stas Mishchenkov@2:460/5858 to Charles Pierson on Tue Oct 13 00:25:54 2020
    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)