/ns /cs and other shorthand IRC commands not recognised.

[elpasi]

Shorthand access to servs is not recognised in adium IRC< and I believe this to be a major mistake as I just typed an /ns command and everyone saw the password I tried to identify with. Please add support for these so other people don't get caught out too! Luckily, I use a different password in IRC so this didn't go too far, but many people are less secure and may use the same password for many critical things (And I'd hate to see that happen)

[cbarrett]

Why would this be waiting on libpurple? We can implement commands like these Adium-side if necessary.

[am]

Yes, but the clean solution would be to implement that in libpurple.

Of course, we could do nearly everything in the "waiting for libpurple" milestone by doing the protocols ourselves by using the hooks for receiving and send_raw to send our stuff, but that would hardly be a clean solution.

[cbarrett]

Replying to am:

Yes, but the clean solution would be to implement that in libpurple. Of course, we could do nearly everything in the "waiting for libpurple" milestone by doing the protocols ourselves by using the hooks for receiving and send_raw to send our stuff, but that would hardly be a clean solution.

Sure, but there are plenty of people who can fix this issue in libpurple. It's not like we're waiting on them to fix or add something that we cannot do. In fact, /nickserv and /chanserv already exist as commands.

[zacw]

(In [26585]) The expectation on IRC is different than most anywhere else. If we don't have an internal command for a /command, send it to the server; don't ever send anything starting with "/" to a channel. This also has the added benefit of making /commands work in queries on IRC. Fixes #10904 (for servers which have NS/CS aliases)

[Robby]

(Part of "Twitter Support")