soju forked to be LESS SHIT
e9cebb6fe3
Unfortunately, I don't think there's a good way to implement net.Conn semantics on top of channels. The Close and SendMessage methods should gracefully fail without panicking if the connection is already closed. Using only channels leads to race conditions. We could remove the lock if Close and SendMessage are only called from a single goroutine. However that's not the case right now. Closes: https://todo.sr.ht/~emersion/soju/55 |
||
---|---|---|
cmd | ||
config | ||
doc | ||
.build.yml | ||
.gitignore | ||
bridge.go | ||
conn.go | ||
db.go | ||
downstream.go | ||
go.mod | ||
go.sum | ||
irc.go | ||
LICENSE | ||
logger.go | ||
Makefile | ||
README.md | ||
ring.go | ||
server.go | ||
service.go | ||
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
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 doc/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