You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If database returns registration, require password.
If database returns no registration, do not require password or prefix, allow user to use the nickname as it is not registered.
Is it possible please that someone could help us with this request, I was thinking that just an option to the existing module could be added on whether to require the Guest prefix or not, rather than an entirely new module for very similar purpose, but ...
Alternatively, possibly the module can 'fix' it for the user and add the Guest prefix when the database returns no registration but the user did not use the Guest prefix. Either way, I do not think disconnecting users because they tried to connect using an unregistered nickname is correct ...
The text was updated successfully, but these errors were encountered:
It sounds like you'd be better off using a services package (ex. Anope or Atheme). m_sqlauth 's purpose is to control connections to the server, which you sound to not really want.
@genius3000 the ability to allow Guests is already in the module, I just want to remove the requirement to have them prefixed with the Guest_ string. We don't run services as have no need; permanent channels only, web chat only etc. Installing that would definitely be an overkill for our needs, hence requesting this small change to the existing module.
We have tried using https://github.com/inspircd/inspircd/blob/v2.0.26/src/modules/m_sqlauth.cpp but basically users are confused about having to use the Guest prefix to be able to connect when they don't want to register.
We want the module to work like this:
Is it possible please that someone could help us with this request, I was thinking that just an option to the existing module could be added on whether to require the Guest prefix or not, rather than an entirely new module for very similar purpose, but ...
Alternatively, possibly the module can 'fix' it for the user and add the Guest prefix when the database returns no registration but the user did not use the Guest prefix. Either way, I do not think disconnecting users because they tried to connect using an unregistered nickname is correct ...
The text was updated successfully, but these errors were encountered: