From 4ef4eaeb42acde7c9dfffc5cd4f1c53635ba70ea Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Thu, 27 Mar 2025 01:55:45 -0600 Subject: [PATCH] Update proposals/4279-service-notice-rooms.md Co-authored-by: Johannes Marbach --- proposals/4279-service-notice-rooms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4279-service-notice-rooms.md b/proposals/4279-service-notice-rooms.md index d6ca43937..1e99efc7a 100644 --- a/proposals/4279-service-notice-rooms.md +++ b/proposals/4279-service-notice-rooms.md @@ -216,7 +216,7 @@ most possible while an older server and newer client are in use: the server does to be filtering the room, and the client is simply responding to input it was given. An approach for fixing this would be for the client to check the supported specification versions by -the server, determining whether the filtering code *should *be present. If the server doesn't support +the server, determining whether the filtering code *should* be present. If the server doesn't support the relevant specification version (or newer), the client should disable server notice room support. A future MSC may also create ways to verify the creator/sender, allowing the server to drop its filter.