Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't intercept /(c|h|n)s shortcut commands #153

Closed
dgw opened this issue Mar 6, 2016 · 2 comments · Fixed by #154
Closed

Don't intercept /(c|h|n)s shortcut commands #153

dgw opened this issue Mar 6, 2016 · 2 comments · Fixed by #154
Assignees
Labels
Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors.
Milestone

Comments

@dgw
Copy link
Contributor

dgw commented Mar 6, 2016

Intercepting /ns, /cs, and /hs and converting them to PRIVMSGs means the application has to assume that the services will have the expected names. There is a risk of the user accidentally sending a services command to another user who is using a common services nickname on a network that doesn't follow the convention.

By contrast, passing through /ns, /cs, and /hs to the server directly will either execute the services command as expected, or fail with an unknown command response—at which point the application can either retry using the conventional name of the service (more user-friendly) or pass the failure on to the user (safer).

Generally I'm in favor of aliases, but personally I'd rather risk a failed /ns identify command than risk The Lounge silently sending my password to an unknown user squatting on the name nickserv.

As a side note, it's also not entirely fair to Rizon that /bs isn't intercepted also. 😛

@maxpoulin64 maxpoulin64 added the Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors. label Mar 6, 2016
@maxpoulin64 maxpoulin64 self-assigned this Mar 6, 2016
@maxpoulin64
Copy link
Member

Yeah this is a known issue 👍. Command overhaul is a project that will likely happen relatively soon. I was supposed to work on that today but #152 took a bit more time than I expected. I might give it a shot tomorrow if xPaw haven't done it already.

@dgw
Copy link
Contributor Author

dgw commented Mar 6, 2016

Glad to hear this is on the radar. 👍

@astorije astorije added this to the 1.4.0 milestone Oct 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants