Cinny supports MatrixRTC

[spaetz]

Project Affected

https://github.com/cinnyapp/cinny

Current Information

It claims no support for VOIP

Suggested Correction

MatrixRTC has been included on March 7, by adding a bundled element-call

Source

cinnyapp/cinny#2680

Additional Context

Ideally, the ecosystem would be able to distinguish between legagy calls and MatrixRTC calls

[HarHarLinks]

indeed there are some more clients that also support element call. we do have a grandfathered-in flag for jitsi support. i am overall wary of advertising off-spec features given their instability, incompatibility, etc.

users are already frequently confused by element call being advertised as if it was stable, only to discover that matrixrtc isn't, isn't in other clients, and the calls from their one client aren't compatible with those in another. overall the questions i ask myself is:

• does help matrix's messaging in general to advertise some unstable features, say the matrix 2.0 features, on the website?
• would it help user confusion if we added a third calls flag for matrixrtc to the website list of clients?

[velikopter]

I think we should wait until MatrixRTC and Element Call are stable before we add it to client features list.

[spaetz]

I agree that the situation is confusing. For me, that is one more reason to explicitely distinguish between "jitsi" and "matrix RTC" support. legacy 1:1 is basically unsupported with the exception of EW, and MatrixRTC has been adopted by quite a few clients by now, more importantly, VOIP is one of those features that users apparently find very important, so it is an adoption criteria.
MatrixRTC not yet being stable is a problem, yes. But if we name the category "element call", we could mark all clients that bundle (or use) element call.

But then I will defer to you, whatever call you make, I am fine with it :-)