Skip to content

Commit 2c6ddaf

Browse files
authored
Clarify the meaning of "public rooms" for call invites (#2106)
1 parent fc81171 commit 2c6ddaf

File tree

2 files changed

+8
-5
lines changed

2 files changed

+8
-5
lines changed
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
"Public" rooms with respect to call invites are defined through their join rule.

content/client-server-api/modules/voip_events.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -202,11 +202,13 @@ specific user, and should be set to the Matrix user ID of that user. Invites
202202
without an `invitee` field are defined to be intended for any member of the
203203
room other than the sender of the event.
204204

205-
Clients should consider an incoming call if they see a non-expired invite event where the `invitee` field is either
206-
absent or equal to their user's Matrix ID, however they should evaluate whether or not to ring based on their
207-
user's trust relationship with the callers and/or where the call was placed. As a starting point, it is
208-
suggested that clients ignore call invites from users in public rooms. It is strongly recommended that
209-
when clients do not ring for an incoming call invite, they still display the call invite in the room and
205+
Clients should consider an incoming call if they see a non-expired invite event
206+
where the `invitee` field is either absent or equal to their user's Matrix ID.
207+
They should, however, evaluate whether or not to ring based on their user's trust
208+
relationship with the callers and/or where the call was placed. As a starting
209+
point, it is RECOMMENDED that clients ignore call invites in rooms with a
210+
[join rule](#mroomjoin_rules) of `public`. When clients suppress ringing for an
211+
incoming call invite, they SHOULD still display the call invite in the room and
210212
annotate that it was ignored.
211213

212214
##### Glare

0 commit comments

Comments
 (0)