This does work fine for me actually.
I have three networks set up this way (in addition to a fourth one which
is BitlBee on localhost).
The buffers are associated with the server alias, not with the server url.
E.g. I talk to BouncerServ@oftc and BouncerServ@libera in buffers with those
I have the exact same server name (i.e. url) as key in three different entries
in server-alist, and the passwords, port, encryption and nick are also the
same, they just have different usernames and server alias (which means it's
not being treated as a real alist, which normally only use the car-most
instance of each key).
If you don't like OFTC you can change it to tilde.chat or any other
contrib/clients.md | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/contrib/clients.md b/contrib/clients.md
index e947046..3df2c85 100644
--- a/contrib/clients.md+++ b/contrib/clients.md
@@ -43,8 +43,17 @@ The only thing needed here is the general config:
:user-name "<username>/irc.libera.chat" ;; Example with Libera.Chat
- :password "<password>")))+ :password "<password>"+ :server-alias "libera")+ ("<server>" ;: same soju server address for both+ :port 6697+ :encryption tls+ :nick "<nick>"+ :user-name "<username>/irc.oftc.net" ;; Example with OFTC+ :password "<password>" ;; same soju password for both+ :server-alias "oftc")))```
+(The password should be your soju password, you'll configure your network passwords by talking to BouncerServ.)Then run `M-x irc`.