seshat
element-call
Our great sponsors
seshat | element-call | |
---|---|---|
5 | 9 | |
80 | 507 | |
- | 5.0% | |
5.2 | 9.9 | |
9 months ago | 1 day ago | |
Rust | TypeScript | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
seshat
-
Element X Matrix client now on iOS early release
> Can you already say something about encrypted search support in Element X?
It's planned, and should be way easier to do than on old Element given we can hook the clientside search indexer (https://github.com/matrix-org/seshat), which happens to be in Rust, directly into matrix-rust-sdk and thence both EIX and EAX. Whereas previously we'd have had to do custom integs with Seshat on EI and EA like the current one on Element Desktop, which just becomes a maintenance nightmare. Hopefully should be ready in the next months.
> Also since you mentioned it, is multiaccount support something that we can realistically expect to see in Element X someday (maybe even in a v1.0?). If I remember correctly for the previous iterations of the clients the status was mostly "maybe one day" or "the architecture does not really support it".
Definitely. We actually had it pre-Element in Matrix Console, and then it got lost in Element. The hope is to get it into Element X relatively early.
-
Matrix Community Year in Review 2022
https://github.com/matrix-org/seshat - we’ve had it for years on desktop; just need to hook it up on mobile. it’s currently blocked behind unifying sdks, so we don’t have to do it twice in iOS & Android.
-
Introducing Native Matrix VoIP with Element Call!
Excellent noise cancellation (and background noise elimination, microphone scratch noise elimination etc). Ideally you need something like https://krisp.ai/ or https://workspaceupdates.googleblog.com/2021/06/background-n... in the mix - but doing this in an E2EE-friendly and privacy preserving manner is Hard. However, just like we solved E2EE full text search by doing it clientside and making the indexes gossipable between your clients (https://github.com/matrix-org/seshat), we'll have a go at doing something similar for this problem too.
-
Native Matrix VoIP with Element Call
The competitive gap with Discord in terms of media quality is probably something like:
* Need a low-latency SFU. This should be very doable; not only are there a lot of good FOSS SFUs to build on top of these days, the history of the Matrix team is actually that we built VoIP stacks fulltime before we shifted focus to Matrix, and we've built MCUs and media servers of all flavours in the past. MSC3401 should also give us a competitive edge given latency will be automagically minimised by using the physically closest decentralised SFU, and letting anyone bring their SFU to the party.
* Needs a SFU with good rate control (and/or FEC). This is probably the single most important thing to get right in terms of quality. Signal wrote up a good overview of why: https://signal.org/blog/how-to-build-encrypted-group-calls/
* Excellent noise cancellation (and background noise elimination, microphone scratch noise elimination etc). Ideally you need something like https://krisp.ai/ or https://workspaceupdates.googleblog.com/2021/06/background-n... in the mix - but doing this in an E2EE-friendly and privacy preserving manner is Hard. However, just like we solved E2EE full text search by doing it clientside and making the indexes gossipable between your clients (https://github.com/matrix-org/seshat), we'll have a go at doing something similar for this problem too.
* Excellent automatic gain control. The importance of normalising/compressing everyone's audio so they're equivalent loudness is really important.
We're also in the process of adding in spatial audio (unsure if Discord has that) which should help a tonne with distinguishing the different audio feeds.
We can probably also be more bullish about supporting new audio codecs like Lyra.
-
Show HN: Beeper – All Your Chats in One App
Messages are stored in encrypted form on the Beeper server and the Beeper client has a local search index (the same one used by Element desktop: https://github.com/matrix-org/seshat)
element-call
-
Omegle is Dead, Let's Build a New One
Let me know what you guys think. You can check out the github here and experiment with it via the first link.
-
Matrix 2.0: The Future of Matrix
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.
-
Zoom terms now allow training AI on user content with no opt out
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.
- Voice rooms in Element ?
-
Discord's AI features violate our privacy, and it's time we pushed back.
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
-
Are there any good team communication apps like Slack that have open voice channels Like Discord, but not Slack/Discord? I cannot seem to find any.
Element Call github
-
Introducing Native Matrix VoIP with Element Call!
With screening for unapproved callers, this would really replace every other platform!
-
Native Matrix VoIP with Element Call
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.
What are some alternatives?
matrix-docker-ansible-deploy - 🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
matrix-js-sdk - Matrix Client-Server SDK for JavaScript
rnnoise-wasm - rnnoise noise suppression library as a WASM module
maubot - A plugin-based Matrix bot system.
matrix-spec-proposals - Proposals for changes to the matrix specification
matrix-doc - Proposals for changes to the matrix specification [Moved to: https://github.com/matrix-org/matrix-spec-proposals]
Matrix-EmailBridge - A bridge written in Golang to receive and write emails in matrix
rust-synapse-compress-state - A tool to compress some state in a Synapse instance's database
FedCM - A privacy preserving identity exchange Web API