@matrix No,Gitter does *not* natively speak Matrix.While your new bridge has become really nicely integrated,it's still only a bridge using a Synapse instance on the backend.I would have liked it to see the Gitter software becoming a full Matrix homeserver software.I prefer the look and feel and especially the performance of Gitter over that of Synapse and Element.It would have been a great opportunity to be able to run a own instance of the Gitter software that federates with the Matrix network.Now Gitter will completely die in favor of Synapse and Element.That's sad 😢
@nipos yes, you have to have a homeserver somewhere to speak Matrix. We could have embedded one into Gitter, or just have Synapse/Dendrite sitting alongside it. Using one sitting alongside is easier. Gitter isn't going to "completely die" at all; and if we fail to converge Element & Gitter's UI, then we'll keep the Gitter engine running. Meanwhile, anyone can continue to run their own Gitter, with their own homeserver is they want, whatever happens on Gitter.im.
@matrix I think you're missing my point.Yes,I can run my own Gitter but then I still need Synapse which has huge performance issues.With the announcement that you buy Gitter,I hoped that Gitter will become a alternative to Synapse with it's high-performance backend.And you said that Gitter the software will be replaced by Synapse and Element yourself so Gitter the software will die.Gitter the platform will stay alive but only as one of many Matrix instances.I really like Matrix and run three instances currently but I think more diversity in software would be good for the protocol.
@nipos Synapse's performance issues are way improved these days, as per https://matrix.org/blog/2020/11/03/how-we-fixed-synapses-scalability.
Generiere Instanz-Beschreibung... ... ... ... ... ERROR 418!