mirror of
https://github.com/Mikaela/Limnoria-doc.git
synced 2024-11-26 22:39:25 +01:00
use/getting_started.rst: mention that NickAuth...
...identify you automatically.
This commit is contained in:
parent
320d16e191
commit
66b1b2c976
@ -172,8 +172,14 @@ freenode. The syntax is [<network>] <bot-username> <NickServ-account>::
|
|||||||
<Mikaela> +nickauth nick add freenode Mikaela Mikaela
|
<Mikaela> +nickauth nick add freenode Mikaela Mikaela
|
||||||
<Yvzabevn> OK.
|
<Yvzabevn> OK.
|
||||||
|
|
||||||
Next time when I identify to NickServ I can use the NickAuth Auth command
|
Next time when I identify to NickServ I will get identified automatically
|
||||||
to also identify to the bot::
|
if the bot sees that I was identified when I joined. This requires server
|
||||||
|
to support extended-join and WHOX. Most of modern networks support
|
||||||
|
them, but if your bot is using some bouncer, it might not support them.
|
||||||
|
|
||||||
|
Automatic identification doesn't work always even when it's supported, but
|
||||||
|
when it fails, I can always use the NickAuth Auth command to identify to
|
||||||
|
the bot::
|
||||||
|
|
||||||
<Guest45020> +whoami
|
<Guest45020> +whoami
|
||||||
<Yvzabevn> I don't recognize you. You can messsage me either of these two commands: "user identify <username> <password>" to log in or "user register <username> <password>" to register.
|
<Yvzabevn> I don't recognize you. You can messsage me either of these two commands: "user identify <username> <password>" to log in or "user register <username> <password>" to register.
|
||||||
|
Loading…
Reference in New Issue
Block a user