@JJGadget
Element X takes 245MB… download from github… puh…
But the install-advice for the sliding-sync server is a bit unclear for me… i tried to install it… huh… no idea, how to do it.
Should it run on an own vserver?
Or can i run it on the same server as my matrix-synapse is running?
when yes… why is it also listening on port 8008 as synapse is listening?
You can have it listen in lieu of Synapse, or it can live side by side on the same server (thus not breaking compatibility with older clients) and you can just point Element X to the new port.
Yep, just finished setting up sliding-sync myself (I’m old fashioned so I still use Apache 😄)
The initial sync was slower, but even slower for me as the initial sync caused RAM spikes leading to the OOM killer sneaking in. Had to set up a swap file to temporarily get past it.
Also, note that the initial sync is slow because it does a full V2 sync to the proxy first, only then can you start with V3/Sliding-Sync.
But, Element X seems fun! Not ready to be a daily driver for me (I really need proper spaces support for the way I use Matrix), but damn if the new loads aren’t sweet.
Edit: Oh man, just installed Element X on another device to test a “clean” login (since the V2 sync is already completed, now). Probably took ~5s from first time logging in to seeing every chat/message. Goddamn that’s sexy. I’m a happy camper, right now.
deleted by creator
@jakob @JJGadget there are apk downloads. I added https://github.com/vector-im/element-x-android to obtanium. Source is here https://github.com/vector-im/element-x-android/releases
deleted by creator
deleted by creator
@jakob @JJGadget that is bad but it has to get on par with other apps to compete. No google deppendency isn’t good if noone is using it
deleted by creator
deleted by creator
@jakob @JJGadget nice 👍🏻 it’s not m fault 😀
deleted by creator
Element is on f-droid. Hopefully Element X shows up soon.
@JJGadget
Element X takes 245MB… download from github… puh…
But the install-advice for the sliding-sync server is a bit unclear for me… i tried to install it… huh… no idea, how to do it.
Should it run on an own vserver?
Or can i run it on the same server as my matrix-synapse is running?
when yes… why is it also listening on port 8008 as synapse is listening?
github.com/matrix-org/sliding-…
I used this video to set up sliding sync on my personal server.
https://youtu.be/25wkV2ZCSsM?si=-nNvU5jgAI_wSzyh
You can have it listen in lieu of Synapse, or it can live side by side on the same server (thus not breaking compatibility with older clients) and you can just point Element X to the new port.
@derin
I run nginx in front of synapse and sliding-sync
And the initial sync was VERY slow…
🤔🤔
Yep, just finished setting up sliding-sync myself (I’m old fashioned so I still use Apache 😄)
The initial sync was slower, but even slower for me as the initial sync caused RAM spikes leading to the OOM killer sneaking in. Had to set up a swap file to temporarily get past it.
Also, note that the initial sync is slow because it does a full V2 sync to the proxy first, only then can you start with V3/Sliding-Sync.
But, Element X seems fun! Not ready to be a daily driver for me (I really need proper spaces support for the way I use Matrix), but damn if the new loads aren’t sweet.
Edit: Oh man, just installed Element X on another device to test a “clean” login (since the V2 sync is already completed, now). Probably took ~5s from first time logging in to seeing every chat/message. Goddamn that’s sexy. I’m a happy camper, right now.