258
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Sep 2023
258 points (98.1% liked)
Technology
59300 readers
798 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
I don't get how this works in relation with Element X. Surely, installing and using Element X is not sufficient to use Matrix 2.0 protocols is it? I mean, it must depends on the room version and the like, right?
Element X implements most of the client side stuff mentioned above, but it doesn't depend on a specific room version: instead, your homeserver must implement/run an additional service (a "sliding sync" proxy, a special binary written in Go that is deployed alongside Synapse) and then advertise that service's existence.
If it does the latter, Element X will know where to connect and will function.
Note that this is only temporary so that people can make use of Sync V3 before it officially lands in Synapse. And it, technically, isn't synapse exclusive either, as it's its own thing.
OK, it's clearer now, thanks for the explanation!
It depends on your server and whether they've/you've enabled SlideSync.