FedCM VS element-call

Some federated identity protocols, including SAML, depend on third party cookies. I've been watching the Federated Identity W3C community group work through some of the issues for a couple of years.

You all might be interested in checking out their GH repo: https://github.com/fedidcg/FedCM

Related to this specification https://fedidcg.github.io/FedCM/

Some of us are proactively working on this problem [1]. Not trivial, but I think we are making forward progress to reconcile and mediate login in browser UX.

[1] https://github.com/fedidcg/FedCM/blob/main/meetings/2021/Web...

That's precisely where I've been using them the most :)

https://fedidcg.github.io/FedCM

Not for everybody, I agree, but it is kinda of ironic that you mentioned "may be like an IETF proposal." :)

Also, technical blog posts, e.g.

https://code.sgo.to/2022/04/11/metamath.html

Has support for IndieAuth and/or FedCM (when stable enough) been considered?

https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web

https://github.com/fedidcg/FedCM

Let me know what you guys think. You can check out the github here and experiment with it via the first link.

Looks like there's an open protocol and an open source client implementation for video calls. https://github.com/vector-im/element-call

This is great! Jitsi has never clicked for me. I tried it a few times, and read about it, and was never excited about it. I just tried Element Call, albeit an empty room, and the UI feels right.

There's now also https://github.com/vector-im/element-call.

They have SFU support as of recently, so it should work scale similarly to Jitsi et al.

Would second recommending giving Matrix a try, native voip is actively being worked on in the form of Element Call. But to access it in Element you currently have to use the develop client. Otherwise you have to use 3rd party voip software in the form of Jitsi in the stable release.

Element Call github

With screening for unapproved callers, this would really replace every other platform!

Currently we don't force TURN, so in practice this means that voice packets go direct between the clients if possible, and so the IP addresses of the clients are necessarily exposed to each other.

However, this is utterly trivial to fix: matrix-js-sdk already exposes https://github.com/matrix-org/matrix-js-sdk/blob/96ba061732b... and we simply haven't exposed it as a setting in Element Call yet. I've filed a bug for it at https://github.com/vector-im/element-call/issues/251 - thanks for bringing it up!

In terms of moderation: this is no different to moderation in Matrix as a whole, where we're already busy working on shared greylists (MSC2313 and friends) - https://matrix.org/blog/2020/10/19/combating-abuse-in-matrix... has more details at the end.