sad/soju
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: clarify that client suffixes are not required for chathistory

Browse Source
This commit is contained in:
Simon Ser 2023-08-17 18:25:07 +02:00
parent 1a1610c1ce
commit c06d97ab9b
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/soju.1.scd
View File

@ -24,8 +24,10 @@ setup one connection per server configured in soju, and indicate the network
name in the username: "<username>/<network>". Then channels can be joined and name in the username: "<username>/<network>". Then channels can be joined and
parted as if you were directly connected to the upstream server. parted as if you were directly connected to the upstream server.
For per-client history to work, clients need to indicate their name. This can For per-client history to work on clients which don't support the IRCv3
be done by adding a "@<client>" suffix to the username. _chathistory_ extension, clients need to indicate their name. This can be done
by adding a "@<client>" suffix to the username.
When joining a channel, the channel will be saved and automatically joined on When joining a channel, the channel will be saved and automatically joined on
the next connection. When registering or authenticating with NickServ, the the next connection. When registering or authenticating with NickServ, the
credentials will be saved and automatically used on the next connection if the credentials will be saved and automatically used on the next connection if the