<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    This message is in my motd_nor<br>
    It will be displayed if you use set/var $main::passwdreq = 0<br>
    But until now no one reacted by asking me to set a password.<br>
    <br>
    _________________________________________________________________<br>
    #################################################################<br>
    You are not registered to this cluster<br>
    Please register first and use a password to login.<br>
    You can apply for a password by contacting sysop at xxxx.xx<br>
    IF YOU DO NOT WANT TO REGISTER YOU STILL CAN USE THE CLUSTER<br>
    BUT YOU CANNOT SEND SPOTS.<br>
    ################################################################<br>
    ________________________________________________________________<br>
    <br>
    <br>
    73<br>
    Jan<br>
    PA4JJ<br>
    <br>
    <br>
    <div class="moz-cite-prefix">Op 6-3-2025 om 08:59 schreef Faizul via
      Dxspider-support:<br>
    </div>
    <blockquote type="cite"
cite="mid:7866a99a.AW4AAGXXLbIAAAAAAAAAA8NI7WwAAYKHzrAAAAAAAChsmwBnyVYg@mailjet.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div class="gmail_default" style="font-family:trebuchet
          ms,sans-serif;font-size:small">Agreed, OM. I just want to
          know, is there anything wrong with requiring users to register
          with a password as a standard in DX clustering?</div>
      </div>
      <br>
      <div class="gmail_quote gmail_quote_container">
        <div dir="ltr" class="gmail_attr">On Thu, Mar 6, 2025 at 3:55 PM
          IZ2LSC <<a href="mailto:iz2lsc.andrea@gmail.com"
            moz-do-not-send="true" class="moz-txt-link-freetext">iz2lsc.andrea@gmail.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">
            <div>I think that recent flooding (hundreds of spots per
              second) was not generated by an "entity" connected as a
              user.</div>
            <div>Here there is already a rate limiter on command a user
              can send in a certain interval.</div>
            <div>Just to set the expectation about enforcing the
              password policy.</div>
            <div><br>
            </div>
            <div>73s</div>
            <div>Andrea</div>
            <div>iz2lsc</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>
              <div dir="ltr" class="gmail_signature">--></div>
            </div>
            <br>
          </div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Thu, Mar 6, 2025 at
              7:45 AM Faizul via Dxspider-support <<a
                href="mailto:dxspider-support@tobit.co.uk"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">dxspider-support@tobit.co.uk</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div dir="ltr">
                <div class="gmail_default"
                  style="font-family:"trebuchet
                  ms",sans-serif;font-size:small">
                  <p>Dear DX Spider Community,</p>
                  <p>I’d like to start a discussion regarding the idea
                    of informing users to register before they can use
                    the spot function. While security is important, it
                    is equally crucial that users are aware of such
                    policies to avoid confusion.</p>
                  <p>If some nodes enforce <code>set/register</code>
                    while others do not, users might unknowingly jump
                    from one node to another without understanding why
                    they are unable to send spots. To improve
                    transparency, I propose that we add a notice about
                    this requirement in the <strong>Message of the Day
                      (MOTD)</strong> and also announce it using <strong>ANN</strong>.
                    This way, users are properly informed rather than
                    being caught off guard.</p>
                  <p>We are in the AI era now, and it is easier than
                    ever for someone to use an AI chatbot to generate a
                    script that automatically posts spots using random
                    callsigns. Without proper user registration, this
                    could lead to abuse and affect the integrity of the
                    cluster. While security measures are necessary, we
                    must also ensure that users understand what is
                    happening and why these policies are in place.</p>
                  <p>This is just a discussion, and I’d love to hear
                    your thoughts on the best way to approach this.</p>
                  <p>73,<br>
                    Faizul "Piju" 9M2PJU</p>
                </div>
              </div>
              <img
src="https://sps6s.mjt.lu/oo/AVcAAGPuuVYAAAAAAAAAA8NI7WwAAYKHzrAAAAAAAChsmwBnyUSOyh0GMqlWQ52AKsMwtliIDgAlgMw/b7a54e12/e.gif"
                alt="" style="height: 1px; width: 1px; border: 0px;"
                moz-do-not-send="true" width="1" height="1" border="0">
              _______________________________________________<br>
              Dxspider-support mailing list<br>
              <a href="mailto:Dxspider-support@tobit.co.uk"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">Dxspider-support@tobit.co.uk</a><br>
              <a
href="https://sps6s.mjt.lu/lnk/AW4AAGXXLbIAAAAAAAAAA8NI7WwAAYKHzrAAAAAAAChsmwBnyVYgBbWt_dORSHG9KjsDJH_lygAlgMw/1/KQREHPdIWrSHfmoKH-xzhA/aHR0cHM6Ly9tYWlsbWFuLnRvYml0LmNvLnVrL21haWxtYW4vbGlzdGluZm8vZHhzcGlkZXItc3VwcG9ydA"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
            </blockquote>
          </div>
        </blockquote>
      </div>
      <img
src="https://sps6s.mjt.lu/oo/AW4AAGXXLbIAAAAAAAAAA8NI7WwAAYKHzrAAAAAAAChsmwBnyVYgBbWt_dORSHG9KjsDJH_lygAlgMw/ad6cd9c0/e.gif"
        alt="" style="height:1px;width:1px;border:0;"
        moz-do-not-send="true" width="1" height="1" border="0">
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 77.174.195.163 port 7300
pa4jj-3 77.174.195.163 port 7388</pre>
  </body>
</html>