element-web: enable Element Call by default #275
|
@ -50,4 +50,15 @@
|
|||
# FUTUREWORK: Replace with pub.solar logo
|
||||
auth_header_logo_url = "themes/element/img/logos/element-logo.svg";
|
||||
};
|
||||
# Enable Element Call Beta
|
||||
features = {
|
||||
feature_video_rooms = true;
|
||||
feature_group_calls = true;
|
||||
feature_element_call_video_rooms = true;
|
||||
};
|
||||
element_call = {
|
||||
url = "https://call.element.io";
|
||||
axeman marked this conversation as resolved
|
||||
participant_limit = 50;
|
||||
brand = "Element Call";
|
||||
};
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue
This seems like we'd be sending data to element.io.
We could also try self hosting this, I think its this: https://github.com/matrix-org/waterfall. Although we have to be careful, that service seems to work without any auth, perhaps there is a way to disable this, providing a free-for-all SFU can make someone just drain all our bandwidth.
Or we could change our privacy policy, but it would be sad to remove "We do not share your data to any third party unless in case of federated services...".
I found https://github.com/element-hq/element-call, I think it's superseeds
waterfall
.The currently used
element-web
config looks like this, which is basically our extended version of https://github.com/element-hq/element-web/blob/v1.11.86/config.sample.json. When you start a group call in Element atm you send data to meet.element.io, which we do not mention in our Privacy Policy yet...I think you're raising a valid point and we should fix the Privacy Policy to show the status quo and think about self-hosting a video call solution, like mentioned in #160.
Ah, I didn't realize we were already using it. In which case this shouldn't block this PR.