Getting started

Connect directly to an IRC network or use your soju bouncer to manage upstream networks through one connection.

Direct IRC

For a direct connection to Libera.Chat, add a network with these connection details:

• Host: irc.libera.chat
• Port: 6697
• TLS: on
• SASL: PLAIN with your NickServ credentials, or NONE without SASL authentication.

For a different network, use the connection details supplied by that network. See the README connection examples.

Soju

Point the network at your soju bouncer's host and authenticate with your bouncer account. Use the connection details provided by your bouncer administrator, rather than the direct Libera.Chat settings above.

motd negotiates capabilities with soju and discovers and manages its upstream networks over a single connection using soju.im/bouncer-networks. Available history, read-state synchronization, and push delivery depend on the capabilities your bouncer advertises.

See the bouncer connection documentation. If you use CLoak instead, follow the CLoak guide; its setup and capabilities differ.

History and delivery

On supporting servers, draft/chathistory lets motd page through message history and draft/read-marker synchronizes read state across devices. These features are negotiated with the server, not guaranteed on every connection. Plain networks still work with local-only history and a persistent IRC socket.

Background push delivery requires a soju bouncer advertising soju.im/webpush and a UnifiedPush distributor such as ntfy. Connect motd to soju at least once so it can detect Web Push support, then follow the push notification setup.

motd closes a network's IRC socket only after soju acknowledges its current push endpoint and encrypted test delivery succeeds. Until then, or if Web Push is unsupported or registration fails, that network stays connected through the foreground service. The delivery setting remains UnifiedPush and the status card reports socket fallback.

Soju sends push notifications for direct messages and channel highlights. Ordinary channel traffic is fetched through CHATHISTORY when motd returns to the foreground. Opening the app reconnects first, runs catch-up, and keeps the socket available while you use it. Push payloads are encrypted by soju and decrypted on your device; ntfy cannot read the IRC message.

Read the documented capabilities and full ntfy delivery guide for details and troubleshooting.

Next steps

• Set up and verify push notifications for a compatible soju bouncer.
• Follow the CLoak guide for a CLoak connection and its compatibility limits.
• Configure SOCKS5, Tor, or VLESS + REALITY if your connection needs obfuscation.
• Explore appearance and configuration backups.

For technical detail, see the repository guides for ntfy, CLoak, and obfuscation.