Remove unused policy room sharing mechanism, as per MSC3844 (#1196)
MSC: https://github.com/matrix-org/matrix-spec-proposals/pull/3844
This commit is contained in:
parent
dc4fd9bdd6
commit
3c45c0aeb4
2 changed files with 1 additions and 12 deletions
1
changelogs/client_server/newsfragments/1196.removal
Normal file
1
changelogs/client_server/newsfragments/1196.removal
Normal file
|
@ -0,0 +1 @@
|
||||||
|
Remove unused policy room sharing mechanism, as per [MSC3844](https://github.com/matrix-org/matrix-spec-proposals/pull/3844).
|
|
@ -76,18 +76,6 @@ joining or peeking the room. Joining or peeking is not required,
|
||||||
however: an implementation could poll for updates or use a different
|
however: an implementation could poll for updates or use a different
|
||||||
technique for receiving updates to the policy's rules.
|
technique for receiving updates to the policy's rules.
|
||||||
|
|
||||||
#### Sharing
|
|
||||||
|
|
||||||
In addition to sharing a direct reference to the room which contains the
|
|
||||||
policy's rules, plain http or https URLs can be used to share links to
|
|
||||||
the list. When the URL is approached with a `Accept: application/json`
|
|
||||||
header or has `.json` appended to the end of the URL, it should return a
|
|
||||||
JSON object containing a `room_uri` property which references the room.
|
|
||||||
Currently this would be a `matrix.to` URI, however in future it could be
|
|
||||||
a Matrix-schemed URI instead. When not approached with the intent of
|
|
||||||
JSON, the service could return a user-friendly page describing what is
|
|
||||||
included in the ban list.
|
|
||||||
|
|
||||||
#### Events
|
#### Events
|
||||||
|
|
||||||
The `entity` described by the state events can contain `*` and `?` to
|
The `entity` described by the state events can contain `*` and `?` to
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue