-
Notifications
You must be signed in to change notification settings - Fork 731
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
Cleanup config #5254
Cleanup config #5254
Conversation
Matrix SDKIntegration Tests Results:
|
@@ -21,7 +22,7 @@ | |||
<string name="pusher_app_id" translatable="false">im.vector.app.android</string> | |||
|
|||
<!-- preferred jitsi domain --> | |||
<string name="preferred_jitsi_domain" translatable="false">jitsi.riot.im</string> | |||
<string name="preferred_jitsi_domain" translatable="false">meet.element.io</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
out of interest, is there a ticket with this request? wondering if there's some other tickets we can link to help leave a paper trail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think so. I could have created one, or maybe the people working on the Jitsi configuration could have created issues on each Element clients...
Related PR on EleWeb (I didn't find any issue either):
Cleanup the file config.xml and change default jitsi domain from
jitsi.riot.im
tomeet.element.io
. Jitsi conf are still working. As a bonus I added an icon to this project!