Basic auth processes varying wildly by server is a server/protocol problem, not a client problem, that also manifests itself as /command spam, even if IRC3 theo

Basic auth processes varying wildly by server is a server/protocol problem, not a client problem, that also manifests itself as /command spam, even if IRC3 theoretically solves some of that. Web UIs don't fix that. It also doesn't terribly matter where in the IRC ecosystem the problems lie - the problems exist in said ecosystem, and they've not been effectively fixed. I've tried plenty of web UI clients, and have found them all quite unfortunately mediocre at best. For my part, I've gone so far as to write my own custom IRC client from scratch at one point to fix clientside issues I had - and written my share of utility bots - so hopefully I have some credence when I say I've done my part to try and resolve issues. And yet, I've jumped ship to Discord. Single signin, plenty of customization through bots, history, emoji, inline code blocks... sure, these could all theoretically be solved in IRC with infinite time and energy, but in practice they simply haven't been - and based on the trajectory of the past decade, won't be fixed within my lifetime either. Which leads me to think it's not entirely a technology problem, either. Switching away from the ossified IRC ecosystem may at least partially be a social solution disguised as a technical one. While I'm personally quite skeptical of Matrix as a solution, I applaud the attempt and the experiment. Perhaps I'll be proven wrong.