bab26c7a6f
Downstream and upstream message handling are slightly different because downstreams can send KICK messages with multiple channels or users, while upstreams can only send KICK messages with one channel and one user (according to the RFC). |
||
|---|---|---|
| cmd | ||
| config | ||
| .build.yml | ||
| .gitignore | ||
| bridge.go | ||
| db.go | ||
| downstream.go | ||
| go.mod | ||
| go.sum | ||
| irc.go | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| ring.go | ||
| schema.sql | ||
| server.go | ||
| service.go | ||
| soju.1.scd | ||
| upstream.go | ||
| user.go | ||
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