<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Faizul
</div>
<div class="default-style">
if your MOTD and MOTD.nor are set up correctly and worded correctly, those who login are given a choice,
</div>
<div class="default-style">
MOTD only registered users should see it when they login,
</div>
<div class="default-style">
MOTD.nor is the one to get the message across,
</div>
<div class="default-style">
they can opt to register, or carry on just watching the spots, but unable to send spots,
</div>
<div class="default-style">
i checked my sh/users and 90% are not registered with my node, but are they registered with another node that they have connected too at the same time, which seems to be the norm these days,
</div>
<div class="default-style">
</div>
<div class="default-style">
73 Ken G7VJA
</div>
<div class="default-style">
GB7HTL
</div>
<blockquote type="cite">
<div>
On 03/06/2025 6:44 AM GMT Faizul via Dxspider-support <dxspider-support@tobit.co.uk> wrote:
</div>
<div>
</div>
<div>
</div>
<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 style="height: 1px; width: 1px; border: 0;" src="https://sps6s.mjt.lu/oo/AVcAAGPuuVYAAAAAAAAAA8NI7WwAAYKHzrAAAAAAAChsmwBnyUSOyh0GMqlWQ52AKsMwtliIDgAlgMw/b7a54e12/e.gif" alt="" width="1" height="1" border="0"> _______________________________________________
<br>
Dxspider-support mailing list
<br>
Dxspider-support@tobit.co.uk
<br>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
</blockquote>
</body>
</html>