~emersion/soju#37: 
Detach networks and channels

/msg BouncerServ network|channel detach <name> would hide the network/channel while still staying connected/joined under the hood. This allows to collect history while not actively taking part in discussions.

Status
REPORTED
Submitter
~emersion
Assigned to
No-one
Submitted
2 years ago
Updated
5 months ago
Labels
enhancement

~emersion 2 years ago

commit d9186e994de9a83e6822a5bd08c4640e48e8368b
Author: Simon Ser <contact@emersion.fr>
Date:   Tue Apr 28 15:27:41 2020 +0200

    Add support for detached channels
    
    Channels can now be detached by leaving them with the reason "detach",
    and re-attached by joining them again. Upon detaching the channel is
    no longer forwarded to downstream connections. Upon re-attaching the
    history buffer is sent.

~gildarts 5 months ago

Is the network portion of this still relevant with the removal of multi-upstream and should there be channel detach and channel detach commands for the service in addition to what currently exists?

~emersion 5 months ago

This issue is still open because networks aren't yet detachable. Detached networks would be somehow disabled/hidden in clients.

However I'm not sure it's really something worth it. What are the use-cases for this feature here?

~gildarts 5 months ago

What are the use-cases for this feature here?

Right, that is why I was asking the question. I'm not sure why you would detach a network unless you were using multi-upstream. If you were using single upstream, I assume you would just disconnect your client from that network. That way you aren't removing the network from every client.

Register here or Log in to comment, or comment via email.