-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSC3969: Size limits #3969
MSC3969: Size limits #3969
Conversation
Signed-off-by: Valentin Lorentz <progval plus matrixsignoff at progval dot net> |
Please fix the Rendered link in your OP: - https://github.com/progval/matrix-spec-proposals/blob/size-limits/proposals/proposals/3969-size-limits.md
+ https://github.com/progval/matrix-spec-proposals/blob/size-limits/proposals/3969-size-limits.md |
@progval Have you seen the proposal Bridge limitation warnings and could you add to your Alternatives section a comparison with that? |
I hadn't. The two main differences are that it counts by character, which I mention in the alternatives (and is also not great for IRC), and uses the bridge's state key instead of an empty state key. Using the bridge's key is probably better as it allows stacking limitations of multiple bridges, in addition to explaining to users which bridge is causing the limit. The only downside I see is that it no longer allows admins to set custom limits, except by pretending to be a bridge, but that probably won't be an issue. I'll update this MSC to do the same unless someone objects. |
@Half-Shot Do you have a spec of the bridge limitation format and/or of |
It seems to be MSC2346. |
Rendered
This MSC is meant to signal size limits of platforms bridged to a room to clients in the room, allowing them to display warnings and/or prevent their users from unwittingly sending events that would be bridged either badly or not at all.
This addresses some of the issues mentioned in matrix-org/matrix-spec#836 ; while the rest can be addressed with power levels and MSC3968.