MSC4266: Policies in /.well-known/matrix/support#4266
MSC4266: Policies in /.well-known/matrix/support#4266Johennes wants to merge 1 commit intomatrix-org:mainfrom
Conversation
Signed-off-by: Johannes Marbach <[email protected]>
Johennes
force-pushed
the
johannes/policies
branch
from
4ab463d to
d2e8b7b
Compare
Johennes
changed the title
turt2live
added
proposal
There was a problem hiding this comment.
Implementation requirements:
- Server publishing this
- Client using this
| Instead of querying the server, the client could store the policies in the | ||
| user's account data. If [encrypted] this would prevent the server from tampering | ||
| with the policies the user has consented to. This would, however, not allow | ||
| external users to retrieve the policies. |
There was a problem hiding this comment.
From a homeserver administration and moderation perspective and just a community moderation perspective having access to the policies of remote servers is very useful. Policy documents for a remote server can give an initial impression of if the server has compatible policies with a given community or not.
| If the request is authenticated, the server SHOULD respond with the latest | ||
| version of the policies that the user consented to. |
There was a problem hiding this comment.
On second thought, I suspect this might be tricky to do for .well-known files because these usually contain static content only. A dedicated /policies endpoint might be better after all.
There was a problem hiding this comment.
I think a dedicated policies endpoint would be better. .well-known endpoints are typically served by a webserver, not the homeserver.
4 participants
Rendered
In line with matrix-org/matrix-spec#1700, the following disclosure applies:
I am a Systems Architect at gematik, Software Engineer at Unomed, Matrix community member and former Element employee. This proposal was written and published with my gematik hat on.