~emersion/soju#125: Remove multi-upstream mode

With the soju.im/bouncer-networks extension, clients have a much better alternative to soju's multi-upstream mode.

The multi-upstream mode has several issues:

The biggest IMHO is its cost. It makes the whole bouncer logic complicated and convoluted, with lots of annoying edge cases.
User modes, ISUPPORT, capabilities, case-mapping, and other global per-connection state can't be properly relayed to clients.

Status: RESOLVED CLOSED
Submitter: ~emersion
Assigned to: No-one
Submitted: 3 years ago
Updated: 2 years ago
Labels: No labels applied.

~emersion 3 years ago

Removed LIST support in multi-upstream mode to avoid the complexity cost.

We've discussed with other soju contributors, and decided it's not time yet to remove it completely because soju.im/bouncer-networks support in clients needs to be worked on.

Also see https://todo.sr.ht/~emersion/soju/122.

~emersion 2 years ago

Simon Ser referenced this ticket in commit 9f24f57.

~emersion 2 years ago

Simon Ser referenced this ticket in commit 143dd35.

~emersion 2 years ago

Simon Ser referenced this ticket in commit 1ea3a19.

~emersion REPORTED CLOSED 2 years ago

~pkal 2 years ago

I am disappointed to see this feature removed, while the extension is still described as "experimental". I had issues with my configuration and had to upgrade Soju today, and now my workflow is broken. This was the main feature I started using Soju in the first place.

~sircmpwn 2 years ago

Code's still there, fork it and maintain it as necessary for your needs.

~pkal 2 years ago

"~sircmpwn" outgoing@sr.ht writes:

Code's still there, fork it and maintain it as necessary for your needs.

I guess so, the above comment was written in a hurry so I didn't have the time or the means to inspect the exact changes.