3 ms·
Element X works pretty well on macOS as a desktop client if you have an Apple Silicon Mac. Otherwise, the big Element Web rework is yet to happen. On Android,
by Arathorn 3y ago
Element X works pretty well on macOS as a desktop client if you have an Apple Silicon Mac. Otherwise, the big Element Web rework is yet to happen.
On Android, I can almost guarantee your bug will be fixed: Element X Android doesn’t share any code with Element Android at all, as far as I know (given the former is mainly written in Rust, and the latter is all Kotlin)
- wkat4242 3y agoAh ok no I don't have a Mac, I use FreeBSD :) And thanks I'll try that out!! I really hope it fixes that sync bug. Thanks for all your work on it. It's a great platform.
- Macha 3y agoThis is the second time you've rewritten the Android app with Riot -> RiotX/Element -> ElementX. Just wondering why you throw it away rather than improve it, and if you're at risk of replacing one set of bugs with another?
- mycall 3y agoProbably from too many mistakes and/or new maintainer and/or better ways to do it. Same as it ever was.
- Arathorn 3y agoThe reason for Riot->RiotX (aka Element) on Android was to both move to a modern Android UI idiom, move to Kotlin, and have a well defined storage interface and switch to Rx patterns, whereas the original app had been built somewhat organically. And yes, the maintainer had changed. The reason for Element -> Element X is in order to share precisely the same Rust SDK between iOS and Android (and maybe other platforms in future), so all the heavylifting happens in one single audited codebase, rather than doubling up all the development between iOS and Android, doubling the bug count, etc. It’s also a good opportunity to simplify the data flows, which are surprisingly subtle and performant in a messaging app; I’m not sure how much Rx remains. In this instance, the maintaining team remained the same.
- wkat4242 3y agoUnfortunately it won't connect. I have a home server that I connect to through VPN (not reachable online and with a self signed certificate). The old element asked me to allow the self signed CA but element X says it can't connect. I wonder if this is by design? Getting a let's encrypt cert is very difficult because my server can't get reached from the public internet. I have it that way because I use this one only for bridging and I'd like to keep it safe.