Closed manuroe closed 7 hours ago
Note:
@alice:domain.org
-> https://domain.org/.well-known/element/call.json
Edit All of the above has been accepted by @manuroe and moved to acceptance criteria
Hello,
I was just made aware of this issue, and I wondered what was the rationale in creating a new well-known file versus using the existing .well-known/matrix/client
?
It would have been much easier to use the existing file in ESS, whereas with this solution we need to implement a whole new file just for element call.
It is driven by a separation of concerns between matrix.org homeserver configuration and an element.io service configuration, Element Call here.
Adding this widget_url
parameter to .well-known/matrix/client
would have required to create a new MSC which would have been rejected for the good reason that it is too element.io oriented.
It is driven by a separation of concerns between matrix.org homeserver configuration and an element.io service configuration, Element Call here.
Adding this
widget_url
parameter to.well-known/matrix/client
would have required to create a new MSC which would have been rejected for the good reason that it is too element.io oriented.
Can we come up with a general element well known file that could be use by all the clients we build then ? So that we can add it as a long-term option in ESS ? Because I suppose such a feature could be also very useful to other clients ?
We were not aware that creating new files could be a problem for ESS when we discussed it with @fkwp. Sorry for that.
I am not against having a more global solution using .well-known/element/element.json
. We should probably keep each service configuration nested in the JSON file to avoid future decoding drama.
If we go .well-known/element/element.json
, I would suggest the following JSON format:
{
"call": {
"widget_url": "https://call.server.com"
}
}
Does it work for you @gaelgatelement ? I will update the issue once we agree.
Is it OK to add random keys in .well-known/matrix/client
if their values are prefixed by domain, such as for instance:
{
"io.element.call": {
"widget_url": "https://call.server.com"
}
}
I do not think it requires an MSC in this case?
Discussed in a team meeting, we prefer to keep things separated and implement a separate .well-known/element/element.json
file.
We were not aware that creating new files could be a problem for ESS when we discussed it with @fkwp. Sorry for that.
I am not against having a more global solution using
.well-known/element/element.json
. We should probably keep each service configuration nested in the JSON file to avoid future decoding drama. If we go.well-known/element/element.json
, I would suggest the following JSON format:{ "call": { "widget_url": "https://call.server.com" } }
Does it work for you @gaelgatelement ? I will update the issue once we agree.
I updated the issue with this change. https://github.com/matrix-org/matrix-rust-sdk/pull/3617 implements it.
Will be available on the next EX RC: EXA 0.4.16 and EXI 1.6.13.
Description
Note: This is a temporary solution. In the future, the EC web app content will be fully embedded within the EX app. There will no more need to load it from the Internet. This setting will be then no more required.
The proposal is to use a new
.well-known
file:.well-known/element/element.json
with the following JSON format:Acceptance criteria
.well-known/element/element.json
with thewidget_url
field, the app must use the provided URL to load the EC widget@alice:domain.org
->https://domain.org/.well-known/element/element.json
Leads
Size estimate
S
Dependencies
Out of scope
element.json
will be used for other EC configurations or other Element Service. We focus here onwidget_url
as an initial step.Open questions
Subtasks
Sign-off
Android
iOS
Web