Is this required with synapse v1.114.0 ?

[ubergesundheit]

I am running this proxy along synapse and I am wondering if I can get rid of the sliding-sync proxy once I install synapse v1.114.0

[kegsay]

You need a supported client. Element X nightly builds should have support. For iOS it will default to Synapse during the discovery process during login. Unsure about Android.

[ubergesundheit]

My clients are running Element X from the AppStore. This probably isn't the nightly version, right? So I need to wait until the iOS stable release of Element X enables support for the synapse sliding sync?

[kegsay]

Correct.

[Tealk]

To switch to the native method, simply point the url of org.matrix.msc3575.proxy to the main address.

[youphyun]

I get some conflicting instructions about what's the best way to move from the previous MSC3575 to the new native simplified sliding sync. Which one is better / preferred when it comes to the .well-known/matrix/client?

Maybe the approach will differ based on the Matrix client(s) used?

1. remove the org.matrix.msc3575.proxy entry from the .well-known/matrix/client
   Where do clients get their homeserver configuration from? Are clients able to recognize that the Synapse server has support for the simplified sliding sync if there is no reference to the msc3575.proxy?

2. point the org.matrix.msc3575.proxy entry in the .well-known/matrix/client to the same url as listed in m.homeserver
   For the latest option the feedback I got was that clients may expect the full sliding sync while the latest Synapse server versions have a simplified sliding sync build in.

[nogweii]

Given Element X is now out of beta with support for simplified sync, is the msc3575.proxy entry, and even this project, no longer needed?

[Ezwen]

I would be interested to know as well! I still have the proxy running, but I would like to shut it down. However, a friend tried Element X on his 1.114 instance without proxy, and he told be it did not work. Something is unclear to me.

[Tealk]

@Ezwen What have you tried and what doesn't work?

[z3ntu]

Honestly after reading https://matrix.org/blog/2024/11/14/moving-to-native-sliding-sync/ I still don't know what to do as homeserver admin.

Synapse is on the latest version, as is my Element X on Android but that hasn't prompted the app to migrate to the native sliding sync as described in the blog post. How would I see that it's on the native sync and not on the legacy one also?

I also don't find any reference if something needs to be done in the homeserver configuration, or anything else.

[Tealk]

prompted the app to migrate to the native sliding sync as described in the blog post.

doesn't this only apply to the legacy app?

It works for me without any problems with the following change.

[Szwendacz99]

Honestly after reading https://matrix.org/blog/2024/11/14/moving-to-native-sliding-sync/ I still don't know what to do as homeserver admin.

Synapse is on the latest version, as is my Element X on Android but that hasn't prompted the app to migrate to the native sliding sync as described in the blog post. How would I see that it's on the native sync and not on the legacy one also?

I also don't find any reference if something needs to be done in the homeserver configuration, or anything else.

As far as I remember, Element X on android required sliding sync to work at all, without it, it didn't allow to login. Not sure tho how is it now with it.