On Mon, Feb 20, 2017 at 11:21:50AM +0100, Alberto Garcia wrote: > On Mon, Feb 20, 2017 at 09:33:55AM +0100, Kurt Roeckx wrote: > > > > Could you be a bit more specific about the problems? In my > > > experience it disconnects (infrequently) and it lacks some > > > features, but other than that it's perfectly usable. > > > > See for instance: > > https://github.com/matrix-org/purple-matrix/issues/34 > > Well, that looks like a legitimate bug, but I wouldn't say that it > makes the package unusable. I cannot even reproduce it myself. > > > Anyway, if you disagree with the severity, feel free to close this > > bug. > > I can rename this bug and make it about that tab completion crash that > you reported upstream, but I don't see it as a generic "purple-matrix > is not ready yet".
It's just that each time I mention I'm using this, people tell me taht it's experimental, and probably a bug in purple-matrix. But it's at least not always clear to me where the bugs are, and there seem to be various problems with the homeserver (synapse) too. There are more problems with purple-matrix then that. For instance from the description of the package itself: The following are not yet supported: * Creating new rooms (and one-to-one chats) * Joining existing rooms by alias instead of room_id This is clearly lacking functionality that I expect. I now need to use a different client to join a room. Like I said, if you think that you can support this version for the next 3 years, I have no problem with it. But I wouldn't add it to a stable release yet in it's current state. Kurt
