[Dxspider-support] Discussion: Informing Users About Registration Requirement for Spotting

[Jan]

This message is in my motd_nor
It will be displayed if you use set/var $main::passwdreq = 0
But until now no one reacted by asking me to set a password.

_________________________________________________________________
#################################################################
You are not registered to this cluster
Please register first and use a password to login.
You can apply for a password by contacting sysop at xxxx.xx
IF YOU DO NOT WANT TO REGISTER YOU STILL CAN USE THE CLUSTER
BUT YOU CANNOT SEND SPOTS.
################################################################
________________________________________________________________


73
Jan
PA4JJ


Op 6-3-2025 om 08:59 schreef Faizul via Dxspider-support:
> 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?
>
> On Thu, Mar 6, 2025 at 3:55 PM IZ2LSC <iz2lsc.andrea at gmail.com> wrote:
>
>     I think that recent flooding (hundreds of spots per second) was
>     not generated by an "entity" connected as a user.
>     Here there is already a rate limiter on command a user can send in
>     a certain interval.
>     Just to set the expectation about enforcing the password policy.
>
>     73s
>     Andrea
>     iz2lsc
>
>
>
>
>     -->
>
>
>     On Thu, Mar 6, 2025 at 7:45 AM Faizul via Dxspider-support
>     <dxspider-support at tobit.co.uk> wrote:
>
>         Dear DX Spider Community,
>
>         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.
>
>         If some nodes enforce |set/register| 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 *Message of the Day (MOTD)* and also
>         announce it using *ANN*. This way, users are properly informed
>         rather than being caught off guard.
>
>         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.
>
>         This is just a discussion, and I’d love to hear your thoughts
>         on the best way to approach this.
>
>         73,
>         Faizul "Piju" 9M2PJU
>
>         _______________________________________________
>         Dxspider-support mailing list
>         Dxspider-support at tobit.co.uk
>         https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>         <https://sps6s.mjt.lu/lnk/AW4AAGXXLbIAAAAAAAAAA8NI7WwAAYKHzrAAAAAAAChsmwBnyVYgBbWt_dORSHG9KjsDJH_lygAlgMw/1/KQREHPdIWrSHfmoKH-xzhA/aHR0cHM6Ly9tYWlsbWFuLnRvYml0LmNvLnVrL21haWxtYW4vbGlzdGluZm8vZHhzcGlkZXItc3VwcG9ydA>
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 77.174.195.163 port 7300
pa4jj-3 77.174.195.163 port 7388
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250306/718b1a86/attachment.htm>