soju forked to be LESS SHIT
Go to file
Simon Ser ec26117c08 Relay self-WHO/WHOIS in single-upstream mode
In multi-upstream mode, we can't relay WHO/WHOIS messages for the
current user, because we can't decide which upstream server the
message should be relayed to.

In single-upstream server, we do know which upstream server to use,
so we can just blindly relay the message.

This allows users to send a self-WHO/WHOIS to check their cloak and
other information.
2021-05-20 11:13:14 +02:00
cmd sojuctl: don't use log.Fatalf in readPassword 2021-04-19 14:11:25 +02:00
config Make db and log config options more future-proof 2021-04-21 18:15:04 +02:00
contrib contrib/clients: add gamja and senpai 2021-05-19 16:42:03 +02:00
doc Make db and log config options more future-proof 2021-04-21 18:15:04 +02:00
.build.yml ci: check scdoc is happy 2020-06-10 16:15:20 +02:00
.editorconfig Add .editorconfig 2020-11-30 11:39:41 +01:00
.gitignore doc: document "network delete" 2020-04-01 17:38:09 +02:00
bridge.go Implement casemapping 2021-03-24 18:15:52 +01:00
config.in Make db and log config options more future-proof 2021-04-21 18:15:04 +02:00
conn.go Silence net.ErrClosed errors 2021-05-20 00:07:44 +02:00
db.go db: match placeholders with columns 2021-04-27 09:22:44 +02:00
downstream.go Relay self-WHO/WHOIS in single-upstream mode 2021-05-20 11:13:14 +02:00
go.mod Update dependencies 2021-03-31 18:18:16 +02:00
go.sum Update dependencies 2021-03-31 18:18:16 +02:00
ident.go ident: remove leftover debug log 2020-08-18 17:57:12 +02:00
irc.go Implement CHATHISTORY BETWEEN 2021-05-18 10:44:10 +02:00
LICENSE Switch license to AGPLv3 2020-02-07 17:41:51 +01:00
Makefile Makefile: mark soju and sojuctl as .PHONY 2021-04-27 19:06:16 +02:00
msgstore_fs.go Check message stores implement expected interfaces 2021-05-18 14:19:34 +02:00
msgstore_memory.go Check message stores implement expected interfaces 2021-05-18 14:19:34 +02:00
msgstore.go Implement CHATHISTORY BETWEEN 2021-05-18 10:44:10 +02:00
net_go113.go Silence net.ErrClosed errors 2021-05-20 00:07:44 +02:00
net_go116.go Silence net.ErrClosed errors 2021-05-20 00:07:44 +02:00
README.md readme: mention Makefile, assume soju is installed system-wide 2021-04-19 16:35:18 +02:00
server.go Stop reading X-Forwarded-Port 2021-03-18 13:28:46 +01:00
service.go handleUserDelete: delete the correct user 2021-04-22 10:37:05 +02:00
upstream.go Drop TAGMSG in detached channels 2021-04-20 16:17:28 +02:00
user.go Add per-network logger 2021-04-13 20:12:49 +02:00

soju

builds.sr.ht status

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

See the man page for more information.

Server side

To create an admin user and start soju, run these commands:

sojuctl create-user <soju username> -admin
soju -listen irc+insecure://127.0.0.1:6667

If you're migrating from ZNC, a tool is available to import users, networks and channels from a ZNC config file:

go run ./contrib/znc-import.go <znc config file>

Client side

soju can operate in two different modes: multi upstream and single upstream.

Single upstream mode

In this mode, 1 upstream connection to a irc server = 1 connection to your soju bouncer.

The easiest and fastest way to use this is to specify the address of the server in your username in your client configuration. For example to connect to Freenode, your username will be: <soju username>/chat.freenode.net. Also set your soju password in the password field of your client configuration.

This will autoconfigure soju by adding a network with the address chat.freenode.net and then autoconnect to it. You will now be able to join any channel like you would normally do.

Multi upstream mode

In this mode, a single connection to your soju bouncer can handle multiple upstream connections. You will need to manually configure each upstream connection using the the special BouncerServ user.

Connect to your soju server by specifying your soju username in the username field in your client and your password in the password field.

You should now be able to send private messages to the BouncerServ. You can send it commands to configure soju. Create new networks:

/msg BouncerServ network create -addr chat.freenode.net -name freenode
/msg BouncerServ network create -addr irc.rizon.net -name rizon

You will now be able to join channels on these networks by specifying their name:

/join #soju/freenode
/join #somechannel/rizon

Building and installing

For end users, a Makefile is provided:

make
sudo make install

For development, you can use go run ./cmd/soju as usual.

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 The soju Contributors