1. Forum
  2. FidoNet
  3. FUTURE4FIDO

  • ^RealName: FN LN z:n/f.p

    From August Abolins@2:221/1.58 to Stas Mishchenkov on Tue Sep 22 07:56:00 2020
    Hello Stas!

    ** On Tuesday 22.09.20 - 08:58, Stas Mishchenkov wrote to August Abolins:

    The usual echo rules apply. I realize that some users just
    have aliases in TgM. Some moderators might want the user to
    sign with their real name in that case - unless Stas' gate can
    implement an Alias/RealName conversion?

    It's implemented long time ago.

    === Import 2020-09-22_08-56-49.png Start ===
    begin 644 2020-09-22_08-56-49.png


    OH! Yes.. I remember that. There is a "Name: First Name, Last
    Name" config in TgM. I guess that's what your gate is picking
    up? But if someone were to have that part blank or refuse to
    fill that out, how does your system pick up and maintain the
    real name to meet some echo requirements?

    --
    ../|ug

    --- OpenXP 5.0.46
    * Origin: The future is not what it used to be. (2:221/1.58)
  • From Stas Mishchenkov@2:460/5858 to August Abolins on Wed Sep 23 08:49:06 2020
    Hi, August!

    22 сен 20 07:56, August Abolins -> Stas Mishchenkov:

    OH! Yes.. I remember that. There is a "Name: First Name, Last
    Name" config in TgM. I guess that's what your gate is picking
    up? But if someone were to have that part blank or refuse to
    fill that out, how does your system pick up and maintain the
    real name to meet some echo requirements?

    Each Telegram user has a unique USER ID.

    Have nice nights.
    Stas Mishchenkov.

    --- Бухать - не выход. Но вариант.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From August Abolins@2:221/1.58 to Stas Mishchenkov on Wed Sep 23 08:35:00 2020
    Hello Stas!

    ** On Wednesday 23.09.20 - 08:49, Stas Mishchenkov wrote to August Abolins:

    OH! Yes.. I remember that. There is a "Name: First
    Name, Last Name" config in TgM. I guess that's what
    your gate is picking up? But if someone were to have
    that part blank or refuse to fill that out, how does
    your system pick up and maintain the real name to meet
    some echo requirements?

    Each Telegram user has a unique USER ID.


    That is a good feature. But as a couple of my previous posts
    showed, I can change FN = AA, LN = blank, and FN = August and
    LN = blank in my TgM settings. The TGUID stays the same, but
    the gate can't accomodate the FN + LN requirement for some
    fido echomail areas.

    Maybe the gate can refuse to broadcast a message if the
    LastName is blank?

    --
    ../|ug

    --- OpenXP 5.0.46
    * Origin: The future is not what it used to be. (2:221/1.58)
  • From Charles Pierson@2:240/1120.976 to August Abolins on Wed Sep 23 08:54:06 2020
    Hello, August Abolins.
    On 9/23/20 8:35 AM you wrote:

    That is a good feature. But as a couple of my previous posts
    showed, I can change FN = AA, LN = blank, and FN = August and LN
    = blank in my TgM settings. The TGUID stays the same, but the
    gate can't accomodate the FN + LN requirement for some fido
    echomail areas. Maybe the gate can refuse to broadcast a message
    if the LastName is blank?

    If I am not mistaken, at least most of the Echoes rules that I recall have a caveat about Real Names being in the Body of the message if an alias or handle is in the FN LN section.

    --
    Best regards!
    Posted using Hotdoged on Android
    --- Hotdoged/2.13.5/Android
    * Origin: The Oasis, Houston, Texas, USA (2:240/1120.976)
  • From Richard Miles@2:460/58 to Charles Pierson on Wed Sep 23 19:58:10 2020
    Answering a msg from Charles Pierson:
    Hello, August Abolins.
    On 9/23/20 8:35 AM you wrote:

    That is a good feature. But as a couple of my previous posts
    showed, I can change FN = AA, LN = blank, and FN = August and LN
    = blank in my TgM settings. The TGUID stays the same, but the
    gate can't accomodate the FN + LN requirement for some fido
    echomail areas. Maybe the gate can refuse to broadcast a message
    if the LastName is blank?

    If I am not mistaken, at least most of the Echoes rules that I recall have a caveat about Real Names being in the Body of the message if an alias or handle is in the FN LN section.

    --
    Best regards!
    Posted using Hotdoged on Android

    Yeah, I think your right. As long as you sign it with your real first/last, most mods are okay with it


    Richard Miles


    --- tg2fido.pl
    * Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)
  • From Stas Mishchenkov@2:460/5858 to August Abolins on Thu Sep 24 11:25:16 2020
    Hi, August!

    23 сен 20 08:35, August Abolins -> Stas Mishchenkov:

    That is a good feature. But as a couple of my previous posts
    showed, I can change FN = AA, LN = blank, and FN = August and
    LN = blank in my TgM settings. The TGUID stays the same, but
    the gate can't accomodate the FN + LN requirement for some
    fido echomail areas.

    First, this is not a hard requirement; secondly, now the gate is focused on the Username, but I have almost finished the new version, in which Real Name will be tied to UserID. Only the first name and even three names are allowed in the From field.

    Maybe the gate can refuse to broadcast a message if the
    LastName is blank?

    This is only strictly required in the nodelist. Most users of Telegram leave the last name field empty.

    Have nice nights.
    Stas Mishchenkov.

    --- Старость - это когда видишь сиськи и вспоминаешь, что забыл молока купить
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)