matrix-js-sdk
matrix-appservice
Our great sponsors
matrix-js-sdk | matrix-appservice | |
---|---|---|
7 | 2 | |
1,452 | 129 | |
3.4% | 1.6% | |
9.8 | 0.0 | |
5 days ago | over 1 year ago | |
TypeScript | TypeScript | |
Apache License 2.0 | 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.
matrix-js-sdk
-
Show HN: Mutable.ai – Turn your codebase into a Wiki
I'd quite like some more high level documentation for the Matrix JS SDK (https://github.com/matrix-org/matrix-js-sdk). I've been looking at it for quite some time and still don't understand how timelines work.
- Element (Matrix) adds video/voice rooms
-
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.
-
Introducing Native Matrix VoIP with Element Call!
We expect to turn it on in the next few weeks - the problem we were debugging that we meant it was turned off looks to be fixed. https://github.com/matrix-org/matrix-js-sdk/pull/2002 is the PR that will need to merge to enable it ftr.
-
Mistakes to Avoid Before Submitting Your Pull Request
Unlike any open source projects to which I've contributed, this project involves 2 other repos, matrix-react-sdk and matrix-js-sdk. As explained in the Development guide in the element-web repo, I need those 2 SDKs in order to build Element successfully for code contribution.
matrix-appservice
-
Wechat alternative front end
Use a bridge to matrix https://matrix.org/docs/projects/bridge/matrix-appservice-wechaty you need to trust the hoster of the bridge (server admin) but since we are talking about wechat, there are other problems to focus on
-
Can WeChat be secured?
I dont think this would fly in a corporate setting, but there is a matrix puppeting bridge for wechat. If that doesn't work, there's always the web client.
What are some alternatives?
matrix-react-sdk - Matrix SDK for React Javascript
matrix-appservice-discord - A bridge between Matrix and Discord.
matrix-bot-sdk - TypeScript/JavaScript SDK for Matrix bots
rnnoise-wasm - rnnoise noise suppression library as a WASM module
element-call - Group calls powered by Matrix
wechaty - Conversational RPA SDK for Chatbot Makers. Join our Discord: https://discord.gg/7q8NBZbQzt
element-desktop - A glossy Matrix collaboration client for desktop.
whatsapp - A Matrix-WhatsApp puppeting bridge
seshat - A Matrix message database/indexer
Element - A glossy Matrix collaboration client for the web.