-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Matrix v2 #439
base: testing
Are you sure you want to change the base?
Conversation
Thank you so much @Josue-T for your incredible amount of work these last days. |
Adding my thanks to @Josue-T as well. I am going to test this branch and face the wrath of the 3 friends I convinced to get on my matrix instance 😄 |
Installation went fine, upgrading not so much. |
Normally all port are already open. But well what happen wrong. The upgrade process or the service was not working after the upgrade ? |
The service is running fine. Of course the two bridges (whatsapp & telegram) are not working anymore. |
Do you have some log of theses bridges ? |
Sorry, my bad. I had a second application on the same domain, and that screwed up the installation. |
I created an issue about this here: #443 |
Yes, thank you I found it and succesfully moved synapse to a different domain. |
About change url and domain constraints issue please post your message on #443 |
Hello, I successfully upgraded to this branch. The Sliding Sync proxy's service is enabled and running well. As far as I see Synapse and the slinding sync proxy are installed on the same domain. Unfortunately I can't make Element X on Android connect to my server. My matrix server is running at
When I try to connect Element X to
I'd like to help you with this pull request and adding the sliding sync proxy, by the way thank you for all you've already done. |
Hello, I think you should define the server as |
I tried to login with In nginx logs I see this :
And if I I see no entry in sliding-sync service's journal. |
Hello, Did some test, the issue is linked that Element X don't support CAS and if password authentication is disabled it don't works. By d42f646 it should work now. |
I confirm it works: I could log in Element X, indeed with username and password! |
Great work here! FYI, the sliding sync proxy is no longer required, as Synapse implements (most) of sliding sync. There are still a few missing features for sliding sync in synapse (e.g. it doesn't return pinned events, and a few other things), but most of it should work with an up-to-date ElementX. |
!testme |
Agreed, I planed to remove the proxy and migrate to the native implementation into synapse. But for now I didn't have time to do it. |
!testme |
Just to confirm, is this still the feature that needs to be completed for full element x support? I just updated synapse to the latest version and I'm able to use element x, but it says no push distributors are configured, and I'm not receiving push notifications. |
Well this branch is manly to add all features related to matrix v2 and yes ElementX is matrix v2 client. But about your notification issue I'm not sure that it's related to this branch. |
Oh, okay. Well if element x is supposed to be working with push notifications, should I create a separate issue tracker for this then? |
Well, push notification seem to me not really related matrixv2, but is more general thing which is for now not implemented at all. So yes please create a separate issue about this. |
So, turns out this only affects Android users who have disabled Google Play Services (like me) and can be easily solved by installing NTFY, which is available in the YNH catalog. So, maybe worth a small README PR, if that makes sense. I'll go ahead and submit that, if so. |
Matrix v2 merge
!testme |
!testme |
Matrix V2 Implementation
This is more a tracking page and discussion about Matrix v2 implementation than a pull request.
The target here is to implement all component of matrix V2 so:
The idea here is to provide for user how want a beta version of synapse which will implement theses new feature. Note that this branch will be updated in same time than the testing so user can easily install the branch and get the update as same as than for testing.
frequently asked questions
Why not merging this and making this available to more people ?
Because some component are still really experimental on matrix side. On sliding proxy projet side we have currently theses issues:
How can I use this branch and experiment theses feature ?
As same as for testing you can install the app with this command:
And you can also update the app with this command:
Can I install this without breaking my instance ?
Short answer: the stability of this branch will be same than
testing
Long answer: As same as for testing we try to avoid any issue with these branch and try to keep it stable. But it still be a community project and we can't guarantee the stability of the code. Note also that the stability depends of the upstream code.
When will this be merged into master ?
It depends of the development on package side but also of the upstream on matrix/element side so for now it's difficult to say. In all case the idea is not to merge before all component are ready and tested on the package.
Why adding element-call into this package as there are already a package with this
The idea here is to provide a package with all main feature of matrix configured directly into synapse so there is no more setup to do.
Can I switch back to master or testing branch after doing an upgrade from this branch ?
Nothing was designed for this, so there are a huge risk to break something or that something don't work any-more if you do this. But note that this branch in long term will be merged into
testing
thanmaster
so you won't be blocked if you move to this branch.TODO