ac110eaccc
On some IRC clients, NOTICE messages from a user which does not have a user or host in its prefix (and therefore only have a Name, and look like prefixes of servers), are treated as server notices rather than user notices, and are treated differently. (For that matter, soju also considers NOTICE messages from users with only a Name in their prefix as special server messages). On most of these clients, NOTICE messages from a user are formatted differently and stand out from the large flow of incoming misceallenous server messages. This fills the service user with fake User and Host values so that NOTICE messages from it correctly appear as coming from a user. This is particularly useful in the context of connection and disconnect errors NOTICE messages that are broadcast from the service user to all relevant downstreams. git-svn-id: file:///srv/svn/repo/suika/trunk@220 f0ae65fe-ee39-954e-97ec-027ff2717ef4
soju
A user-friendly IRC bouncer.
- Multi-user
- Support multiple clients for a single user, with proper backlog synchronization
- Support connecting to multiple upstream servers via a single IRC connection to the bouncer
Usage
sqlite3 soju.db <schema.sql
go run ./cmd/sojuctl create-user <username>
go run ./cmd/soju
Then connect with username <username>/chat.freenode.net and join #soju.
See the man page at soju.1.scd for more information.
Contributing
Send patches on the mailing list or on GitHub, report bugs on the issue tracker. Discuss in #soju on Freenode.
License
AGPLv3, see LICENSE.
Copyright (C) 2020 Simon Ser