On Thu, May 27, 2021 at 03:36:03PM +0200, Sasi Olin wrote:
On Thu, May 27 2021 at 15:23:56 +0200, Michal Suchánek <msuchanek@suse.de> wrote:
It might be reasonable to ask if some more recent protocol like Matrix would be less prone to issues like this.
Indeed it is! The issue being that our instance still isn't ready, because our last try to get the authentication working with Bernhard didn't really succeed. I need to steal a SUSE IT employee for an afternoon to set it up one day (which may be hard, considering I assume they are busy)
With more modern protocols with native authentication it might be also easier for people to connect than navigating the baroque maze of antispam measures that have been attached on top of IRC over time.
That would be true, if it wasn't for Matrix clients not implementing SSO for the most part, which is kind of a requirement for us to use the existing login system. I know of 2 clients that implement it in the entire ecosystem. That would be easy to work around if they allowed for authenticating with authentication token provided by another client which is signed in, but sadly that's apparently also pretty rare...
There is a reason for it. For the general user the value of SSO with Matrix is pretty low. You still need your encryption keys to read encrypted rooms (and direct messages) and those aren't on the SSO server. Also if opensuse hosts opensuse rooms on own server but uses federation then people do not need to re-register in the first place because they can access the rooms from whatever homeserver they happened to be registered with. And if one homeserver splits in two that block each other that does not affect the ability of people on either to access the opensuse rooms. Then there is not much point in taking over a home server in the first place and it is much less likely for such situation to evolve. Thanks Michal