Bug 451588

Summary: natively support ZNC networks
Product: [Applications] konversation Reporter: Peter Shkenev <petershh>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: REPORTED ---    
Severity: wishlist CC: argonel
Priority: NOR    
Version: 1.8.21081   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Peter Shkenev 2022-03-16 19:39:35 UTC 
SUMMARY
Konversation identifies networks in its list by combination of server address, port and password. This leads to inconveniences when using Konversation to connect to ZNC.


STEPS TO REPRODUCE
1. Have a ZNC instance with at least two networks configured
2. Add these networks to konversation. They will point to the same address and port.
3. Make these networks use different profiles and add ZNC passwords to these profiles. (ZNC will identify which actual network you want to connect to.)
4. Connect to these networks sequentially

OBSERVED RESULT
Konversation connects to first network as expected, but warns that it is has already connected to the first network before connecting to second.

EXPECTED RESULT
Konversation connects to both networks

SOFTWARE/OS VERSIONS
Linux: Kubuntu 21.10
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2