Mikaela
/
mikaela.github.io
mirror of https://github.com/mikaela/mikaela.github.io/
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update *Un/Setting umodes* 

1. Note that settingumodes to be send to server on connect doesn't apply
   until the next connect.
2. Future happened, so document two methods of setting umodes with
   WeeChat, the old way (traditional would have messed lines) and new
   modern way starting from 1.7+. I am not removing the old way as it
   won't stop working and 1.7 is currently the git version. Also note
   that the umodes can be set per-network.
3. Make ZNC also talk of traditional way (it fit without breaking lines)
   and the modern way linking to issue about it and also clarify that
   which networks the umodes affect depend on which levels you load
   perform.
4. Add missing dot after umode +x which didn't have it even if the other
   umode explanations had it.
This commit is contained in:
Aminda Suomalainen 2016-12-11 16:08:29 +02:00
parent e8d89bbba3
commit 080d141c83
No known key found for this signature in database
GPG Key ID: 0C207F07B2F32B67
1 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
_posts/2015-06-03-setting-umodes.md
View File

@ -18,21 +18,28 @@ an example.*
## Automatic umodes
Umodes aren't remembered across connections so you must configure your
client to (un)set them automatically.
client to (un)set them automatically. **Your umodes won't be change this
way until you reconnect!**
*These examples use the umodes that I am using at the time of writing.*
* HexChat: Open network list, select network and click `edit`, open tab
`Connect commands`, click `add` and type `umode -iI+wRQxg`.
* WeeChat
* now: `/set irc.server_default.command /mode $nick -iI+wRQxg`
* [future?](https://github.com/weechat/weechat/issues/377) *write this
if the future happens.*
* ZNC: `/msg *status loadmod perform` and
`/msg *perform add mode %nick% -iI+wRQxg`
* The same can also be done in webadmin and if you load perform for
user level, adding the command `mode %nick% -iI+wRQxg` will set
umode -iI+wrqXG on all networks.
* Old way: `/set irc.server_default.command /mode $nick -iI+wRQxg`
* Modern way (1.7+): `/set irc.server_default.usermode -iI+wRQxg`
* *For setting umodes only for one network instead of them all
replace server_default with server.name, e.g.*
* `/set irc.server.freenode.usermode -iI+wRQxg`
* ZNC:
* Traditional way: `/msg *status loadmod perform` and
`/msg *perform add mode %nick% -iI+wRQxg`
* The same can also be done in webadmin and if you load perform for
user level, adding the command `mode %nick% -iI+wRQxg` will set
umode -iI+wrqXG on all networks.
* The modes will apply to all networks if you load it on user
level or only the invidual network on network level.
* Modern way: [ZNC issue #1221](https://github.com/znc/znc/issues/1221)
### And what these umodes mean
@ -51,7 +58,7 @@ For what the actual umodes are on your network, try `/quote help umode` or
* R — block PMs from unidentified users (who tend to be spambots and if
they aren't, they can identify to services).
* Q — block channel redirects on Charybdis (mode +f or banforward).
* x — activates IRCd based uncloaking even if it's [not that reliable](https://gist.github.com/maxteufel/1e2cf7ada079c271bd3c)
* x — activates IRCd based uncloaking even if it's [not that reliable.](https://gist.github.com/maxteufel/1e2cf7ada079c271bd3c)
* g — caller-id, people must be `/accepted` or PMed before they can PM you.
More detailed post about that [here]({% post_url 2015-04-02-umodeg %})
and [part 2 here]({% post_url 2015-05-10-umodeg2 %}).