| 1 | # Clients
|
|---|
| 2 |
|
|---|
| 3 | This page describes how to configure IRC clients to better integrate with soju.
|
|---|
| 4 |
|
|---|
| 5 | Also see the [IRCv3 support tables] for a more general list of clients.
|
|---|
| 6 |
|
|---|
| 7 | # catgirl
|
|---|
| 8 |
|
|---|
| 9 | catgirl doesn't properly implement cap-3.2, so many capabilities will be
|
|---|
| 10 | disabled. catgirl developers have publicly stated that supporting bouncers such
|
|---|
| 11 | as soju is a non-goal.
|
|---|
| 12 |
|
|---|
| 13 | # [Emacs]
|
|---|
| 14 |
|
|---|
| 15 | There are two clients provided with Emacs. They require some setup to work
|
|---|
| 16 | properly.
|
|---|
| 17 |
|
|---|
| 18 | ## Erc
|
|---|
| 19 |
|
|---|
| 20 | You need to explicitly set the username, which is the defcustom
|
|---|
| 21 | `erc-email-userid`.
|
|---|
| 22 |
|
|---|
| 23 | ```elisp
|
|---|
| 24 | (setq erc-email-userid "<username>/irc.libera.chat") ;; Example with Libera.Chat
|
|---|
| 25 | (defun run-erc ()
|
|---|
| 26 | (interactive)
|
|---|
| 27 | (erc-tls :server "<server>"
|
|---|
| 28 | :port 6697
|
|---|
| 29 | :nick "<nick>"
|
|---|
| 30 | :password "<password>"))
|
|---|
| 31 | ```
|
|---|
| 32 |
|
|---|
| 33 | Then run `M-x run-erc`.
|
|---|
| 34 |
|
|---|
| 35 | ## Rcirc
|
|---|
| 36 |
|
|---|
| 37 | The only thing needed here is the general config:
|
|---|
| 38 |
|
|---|
| 39 | ```elisp
|
|---|
| 40 | (setq rcirc-server-alist
|
|---|
| 41 | '(("<server>"
|
|---|
| 42 | :port 6697
|
|---|
| 43 | :encryption tls
|
|---|
| 44 | :nick "<nick>"
|
|---|
| 45 | :user-name "<username>/irc.libera.chat" ;; Example with Libera.Chat
|
|---|
| 46 | :password "<password>")))
|
|---|
| 47 | ```
|
|---|
| 48 |
|
|---|
| 49 | Then run `M-x irc`.
|
|---|
| 50 |
|
|---|
| 51 | # [gamja]
|
|---|
| 52 |
|
|---|
| 53 | gamja has been designed together with soju, so should have excellent
|
|---|
| 54 | integration. gamja supports many IRCv3 features including chat history.
|
|---|
| 55 | gamja also provides UI to manage soju networks via the
|
|---|
| 56 | `soju.im/bouncer-networks` extension.
|
|---|
| 57 |
|
|---|
| 58 | # [Hexchat]
|
|---|
| 59 |
|
|---|
| 60 | Hexchat has support for a small set of IRCv3 capabilities. To prevent
|
|---|
| 61 | automatically reconnecting to channels parted from soju, and prevent buffering
|
|---|
| 62 | outgoing messages:
|
|---|
| 63 |
|
|---|
| 64 | /set irc_reconnect_rejoin off
|
|---|
| 65 | /set net_throttle off
|
|---|
| 66 |
|
|---|
| 67 | # [senpai]
|
|---|
| 68 |
|
|---|
| 69 | senpai is being developed with soju in mind, so should have excellent
|
|---|
| 70 | integration. senpai supports many IRCv3 features including chat history.
|
|---|
| 71 |
|
|---|
| 72 | # [Weechat]
|
|---|
| 73 |
|
|---|
| 74 | A [Weechat script] is available to provide better integration with soju.
|
|---|
| 75 | The script will automatically connect to all of your networks once a
|
|---|
| 76 | single connection to soju is set up in Weechat.
|
|---|
| 77 |
|
|---|
| 78 | On WeeChat 3.2-, no IRCv3 capabilities are enabled by default. To enable them:
|
|---|
| 79 |
|
|---|
| 80 | /set irc.server_default.capabilities account-notify,away-notify,cap-notify,chghost,extended-join,invite-notify,multi-prefix,server-time,userhost-in-names
|
|---|
| 81 | /save
|
|---|
| 82 | /reconnect -all
|
|---|
| 83 |
|
|---|
| 84 | See `/help cap` for more information.
|
|---|
| 85 |
|
|---|
| 86 | [IRCv3 support tables]: https://ircv3.net/software/clients
|
|---|
| 87 | [gamja]: https://sr.ht/~emersion/gamja/
|
|---|
| 88 | [senpai]: https://sr.ht/~taiite/senpai/
|
|---|
| 89 | [Weechat]: https://weechat.org/
|
|---|
| 90 | [Weechat script]: https://github.com/weechat/scripts/blob/master/python/soju.py
|
|---|
| 91 | [Hexchat]: https://hexchat.github.io/
|
|---|
| 92 | [Emacs]: https://www.gnu.org/software/emacs/
|
|---|
