91–100 of 130 posts
My family uses Signal for _a lot_, likely way more than we should, and i feel like we'd benefit from threads immensely.
Maybe i should toy with making my own Matrix client or something, heh.
edit: https://github.com/vector-im/element-web/issues/2349 looks like it might exist in some beta form. Depending on the client heh
A bit off topic, but anyone know if Threads are something Matrix currently supports, or ever wants to support? My family uses Signal for _a lot_, likely way more than we should, and i feel like we'd benefit from threads immensely. Maybe i should toy with making my own Matrix client or something, heh. edit : https://github.com/vector-im/element-web/issues/2349 looks like it might exist in some beta form. Depending on…
Alternatives (Fluffychat, for example) are usually a while behind Element because of manpower. For example, native polls are in Element but not in Fluffychat yet. So, if you want to risk the transition, best to recommend the official clients first.
That said, I don't know how well threads will actually work in a family context. I like them as a concept, but outside Google Chat (where every message in a room is a response to or the start of a thread) I haven't seen them get picked up naturally.
A bit off topic, but anyone know if Threads are something Matrix currently supports, or ever wants to support? My family uses Signal for _a lot_, likely way more than we should, and i feel like we'd benefit from threads immensely. Maybe i should toy with making my own Matrix client or something, heh. edit : https://github.com/vector-im/element-web/issues/2349 looks like it might exist in some beta form. Depending on…
A bit off topic, but anyone know if Threads are something Matrix currently supports, or ever wants to support? My family uses Signal for _a lot_, likely way more than we should, and i feel like we'd benefit from threads immensely. Maybe i should toy with making my own Matrix client or something, heh. edit : https://github.com/vector-im/element-web/issues/2349 looks like it might exist in some beta form. Depending on…
Earlier quoted context omitted.
Yup, the grandparent post is a misunderstanding. Basically, we want Element Call to work with a single click to a URL without requiring any account - much as Jitsi and similar do. Therefore it needs to pick a default homeserver. Currently it doesn't play well with existing Matrix accounts (as it will sync in loads of chatrooms which are irrelevant when you just want to do a call), so for expedience we just create acc…
> using your existing server auth Complete sidenote, but just to expand on the above, the OIDC work is particularly exciting because (at least my understanding is) it opens the door for letting people use a single Matrix account for a lot of different "stuff" on top of Matrix. There have been some interesting conversations and demos I've seen about using Matrix rooms to help with P2P sync for apps, and there are alre…
On the basis that "the best code is no code", this could revolutionise app architecture. Imagine if instead of using blockchains, Web3 apps were backed by Matrix servers.
> And, the big one drum roll, please ... we will be integrating this into Element so you can have voice and video rooms, and hold group video calls inside the Element app natively over Matrix. I'd love to replace my teamspeak server with this. Discord is tempting, but I'd rather host it myself.
Mumble works great for me in the meantime
> We’re also working with the Tauri core team to provide cross-platform lightweight desktop apps as soon as possible! How about a lightweight cross-platform Matrix client that doesn't rely on Electron?
There are already like a dozen Matrix clients that don't use Electron. It doesn't take much effort to go to the Clients list and pick one out.
I feel if XMPP just had some better tools this push for Matrix would be unnecessary.
Turns out its much much easier to start from scratch with the right ideas than to transform an existing protocol in to something usable and convince everyone else and update all software to match.
"The market" has decided that Matrix works well and XMPP doesn't. If it made sense to fix XMPP then someone would have done it and we would all be using that.
Earlier quoted context omitted.
The post says there is no E2EE at the moment. They're probably talking about signalling, since with the current implementation of full mesh you get E2EE 'for free' in WebRTC. Also the post mentions: https://2021.commcon.xyz/talks/extending-matrix-s-e2ee-calls...
So in the initial beta we haven't turned on E2EE, purely because it will make it way harder to debug any problems which surface. However, at this rate, things are looking pretty stable and i'd expect us to enable it in the next few weeks. It uses normal Matrix E2EE, which means a Double Ratchet between the pairs of devices participating in a given conversation, which is then used to secure the signalling which is use…