sad/soju
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1,169 Commits 1 Branch 0 Tags 1.6 MiB
d423a1ca24
Commit Graph

1169 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
delthas
5ae1ec5381 Fix network.forEachDownstream exiting on first non-match 
This fixes a serious bug where we stop executing forEachDownstream on
the first downstream that does not match the network. Instead we want to
simply continue; it's a basic filter.
 2022-04-24 18:52:36 +02:00
Frank Steinborn
2a0cc57e3a contrib/clients: Add information about irssi 
Adds information about how to connect irssi to a soju instance,
single-upsteam mode is assumed.
 2022-04-16 08:06:20 +02:00
Simon Ser
42b8dac44e Add user.notifyBouncerNetworkState 
DRY.
 2022-04-15 10:41:38 +02:00
Simon Ser
f3932ab500 Drop user.forEachDownstream 
It's just a for loop.
 2022-04-15 10:32:28 +02:00
Simon Ser
a6636a9b0d Add TODO for upstreamConn.register race 2022-04-15 09:53:30 +02:00
Simon Ser
9fb789ee26 Add timeout for upstream connection registration 2022-04-15 09:49:19 +02:00
Simon Ser
77460dfb97 Split upstream connection handling to separate function 
Just a refactoring, no functional change.
 2022-04-15 09:37:43 +02:00
Simon Ser
2ba13fdefc upstream: use context to set connectToUpstream timeout 
This allows the timeout to apply to the whole sequence of
operations, as opposed to just Dial.
 2022-04-14 19:42:02 +02:00
delthas
b790db1423 Keep batch tag for downstreams with batch cap 
On upstreams without message-tags support, we do not advertise
message-tags anymore. Still, we want to send the batch tag when the
client explicitly requested it.

This fixes a critical issue where we drop the batch tag on chathistory
messages for upstreams that do not support message-tags.
 2022-04-12 17:58:36 +02:00
delthas
683cfe0615 Add support for the SEARCH extension 2022-04-12 17:58:16 +02:00
delthas
b67b9b3cd2 Enable message-tags only when all upstreams support it 
Previously, we would always advertise mesasge-tags. This made
downstreams believe they could send TAGMSG to the upstream, even though
the upstream did not support it.
 2022-04-12 12:41:50 +02:00
delthas
abe5291b62 Add support for the upstream echo-message capability 
This adds support for upstream echo-message. This capability is
enabled when the upstream supports labeled-response.

When it is enabled, we don't echo downstream messages in the downstream
handler, but rather wait for the upstream to echo it, to produce it to
downstreams.

When it is disabled, we keep the same behaviour as before: produce the
message to all downstreams as soon as it is received from the
downstream.

In other words, the main functional difference is that when the upstream
supports labeled-response, the client will now receive an echo for its
messages when the server acknowledges them, rather than when soju acks
them.

Additionally, uc.produce was refactored to take an ID rather than a
downstream.
 2022-04-11 17:27:47 +02:00
delthas
12577c10bb upstream: handle CAP ACK -name 
We'll need this for echo-message.
 2022-04-11 17:27:47 +02:00
delthas
f7a468194d bouncer-networks: Add a read-only error attribute 
This is useful for clients to display additional info abotu why a
network is disconnected.
 2022-04-11 08:38:31 +02:00
delthas
d8ca6d2222 Enable resetting a BOUNCER NETWORK port 
When a client sends BOUNCER CHANGENETWORK with no value (or an empty
port value), this means it wants to reset the port value to its default
value.

Previously we considered an empty port as an actual valid, empty port
value, which would then be used to connect to the server (dial
'example.com:' (ie 'example.com:0'), which failed.
 2022-04-10 18:12:12 +02:00
Simon Ser
17374f2094 doc/getting-started: ask to install soju 
This might seem obvious but… let's add a short sentence just in
case.
 2022-04-06 15:58:16 +02:00
Simon Ser
793ac29571 downstream: use upstream user/host for echo message 2022-04-05 10:09:49 +02:00
Simon Ser
9513c28208 downstream: unify PRIVMSG/NOTICE and TAGMSG codepaths 
They are nearly identical, the only difference is that TAGMSG has
no text parameter.

Inspired from a patch from delthas:
https://lists.sr.ht/~emersion/soju-dev/patches/30651
 2022-04-05 10:09:29 +02:00
Simon Ser
fb20cff45b upstream: pass context to upstreamConn.requestCaps 2022-04-04 13:43:00 +02:00
Simon Ser
5de2a7ec12 Remove unnecessary lastDownstreamID initialization 2022-04-04 09:59:16 +02:00
Simon Ser
846c99dedc Queue WHOIS commands 
This avoids having more than one in flight at a time (avoids
hitting rate limits a bit) and routes back replies to the correct
downstream connection (even if labeled-response isn't supported).

Closes: https://todo.sr.ht/~emersion/soju/193
 2022-04-04 09:58:26 +02:00
Simon Ser
57eb54fb34 upstream: use labeled-response for queued commands 2022-04-04 09:55:32 +02:00
Simon Ser
9f002d0409 server: print panic stack trace as string 
debug.Stack() returns a byte slice.
 2022-04-04 09:54:48 +02:00
Simon Ser
747263fc2d Simplify and improve WHOIS forwarding 
Group together most WHOIS replies. While at it, add a few missing
replies.
 2022-04-04 09:28:04 +02:00
Simon Ser
303c663d02 Refuse to change nick on bouncer connection 
Also simplify the code.

Closes: https://todo.sr.ht/~emersion/soju/192
 2022-04-01 14:55:36 +02:00
Simon Ser
29b1e6f47b downstream: update user realname on SETNAME 2022-03-30 17:51:04 +02:00
Simon Ser
a45f9c3274 Use SETNAME when updating user-wide realname 2022-03-30 15:11:25 +02:00
Simon Ser
d7b5f5d12c downstream: set realname for network-less connections 
Send the user-wide realname config. We still need to handle SETNAME
properly.
 2022-03-30 14:17:09 +02:00
Simon Ser
f6655fbe11 Allow nil network in Get{Nick,Username,Realname} 
Will simplify callers.
 2022-03-30 14:17:09 +02:00
Simon Ser
3d8022d030 doc/getting-started: mention TLS and on-disk logs 2022-03-26 18:42:34 +01:00
Simon Ser
ad8192cb82 doc/getting-started: add paragraph about client names 2022-03-26 18:22:33 +01:00
Simon Ser
8efc125f51 contrib/clients: senpai now supports soju.im/bouncer-networks 2022-03-24 19:19:15 +01:00
Simon Ser
18bb3e6138 doc: split off multi-upstream documentation 
Multi-upstream mode is confusing for new users. Let's explain how
it works in a separate file.
 2022-03-24 19:16:43 +01:00
Simon Ser
0ec3e63ace downstream: send RPL_ENDOFWHO on unmarshalEntity error 
Also remove a couple of outdated comments.
 2022-03-23 19:15:52 +01:00
Simon Ser
44efe37292 downstream: clarify "user not active" error message 2022-03-23 13:11:37 +01:00
Simon Ser
16e43ee3a3 upstream: don't populate time tag for numerics 
Allows us to save a few bytes, e.g. in WHO replies.
 2022-03-22 21:14:02 +01:00
Simon Ser
09513e63fe Remove unnecessary zero initialization 2022-03-22 21:10:06 +01:00
Simon Ser
43371bf347 Add the soju.im/no-implicit-names extension 
References: https://github.com/ircv3/ircv3-ideas/issues/87
 2022-03-22 21:03:20 +01:00
Simon Ser
128aefcc50 downstream: strip back "*" prefix 2022-03-21 17:16:02 +01:00
Simon Ser
8e4c8f7e5a downstream: copy message when degrading extended-join 
Otherwise we mutate the input argument and loops over downstream
connections to send messages will be messed up.
 2022-03-21 17:13:55 +01:00
Simon Ser
5defd29509 Ensure all incoming messages have a prefix set 
Per the spec:

> If the source is missing from a message, it’s is assumed to have originated
> from the client/server on the other end of the connection the message was
> received on.
 2022-03-21 17:01:15 +01:00
Simon Ser
883683c0b7 downstream: always populate downstreamConn.username 
This ensures we don't send a prefix without a username in it.
 2022-03-21 16:37:04 +01:00
Simon Ser
069625d30d downstream: rejigger hostname logic in newDOwnstreamConn 
I find it easier to read this way.
 2022-03-21 16:33:58 +01:00
Simon Ser
e403b88a3d Add support for chghost 2022-03-21 16:30:58 +01:00
Simon Ser
86f08ec35d doc/soju.1: fix syntax error 2022-03-21 16:11:11 +01:00
Simon Ser
78d9a84a6f Add support for RPL_VISIBLEHOST 2022-03-21 16:09:45 +01:00
Simon Ser
b0dbb3cef1 downstream: explain when downstreamConn.sasl is nil 2022-03-21 15:11:43 +01:00
Simon Ser
70ba7032f1 downstream: move negotiatingCaps to downstreamRegistration 
This field is only relevant during connection registration.
 2022-03-21 15:09:31 +01:00
Simon Ser
884bfec6a6 downstream: improve grouping of downstreamConn fields 2022-03-21 15:08:12 +01:00
Simon Ser
b3425ba1a3 downstream: process BOUNCER BIND in downstreamConn.welcome 
This allows clients to send BOUNCER BIND before SASL auth, or to
use BOUNCER BIND with PASS.
 2022-03-21 15:02:54 +01:00