#Weechat commands password
Some services also unidentify you after changing nick (OFTC) or require password for even channel registration. Moreover, using SASL (if possible on server) is a lot better than nickserv.Īnd when services restart or lose your information for some other reason and you aren't reconnected to the server, ENFORCE forces you to change your nick and you must either reconnect or use NickServ and most people probably choose NickServ. I would even say that the security issue would be to send them: that would mean if you mispell any WeeChat command on a channel, it would be sent to the server, which is bad IMHO.Īs the server knows everything you say or do on channels, you probably trust the server or you wouldn't be using it, so I don't see issue with sending misspelled WeeChat commands to server.Īnd why do you say /ns can not be a WeeChat alias? What about /alias ns /quote nickserv (or /alias ns /quote ns)? You are then free to use the alias or not, depending on the server.īecause it would confuse users on servers by giving "ns: unknown command" on not supported servers. WeeChat seems to consider all my commands to be related to server otw. Once you've accomplished this, the page will show a command which you should run in WeeChat. If the page shows a different team than the one you want to add, you can change the team in the top right corner of the page. From my 13 servers all networks that have services have /ns and even one that doesn't have services (it just says "services are temporarily unavailable"). Sometimes I connect to 2 IRC servers in WeeChat: first connect to Freenode and then otw. This command prints a link you should open in your browser to authorize WeeChat with Slack. cannot be WeeChat-side aliases or /quote commands as not all servers have those commands even they are de-facto standard. Even freenode has sometimes had misconfigured servers that have allowed users to take nicknames of services. can be security issue as those server-side commands check that NickServ or whatever service we are accessing is U-lined server and not (malicious) user who has got the nick NickServ on splitted server. If you're used to Slack in the browser then using it through Weechat will be just as easy.
Weechat is very easy to use for a text-based system, it works with the mouse and the commands all have documentation.
Figure 1: Final outcome - Weechat on the Freenode IRC network.
#Weechat commands series
I think that not supporting /ns, /nickserv etc. This is the first post in a series covering Weechat. It also is problematic with some bouncers like ZNC which has /znc command and support for aliases that are also server side and require that to be on. What was the reason for _unknown_commands defaulting to off again? It's issue with commands like /ns that are server side and check that in this case NickServ really is NickServ instead of random user using the nick NickServ. Use saved searches to filter your results more quickly. I asked this at IRC, but never received an answer. We read every piece of feedback, and take your input very seriously.
0 kommentar(er)
