From d620259ac07cb38d43fdbb2880ba47a452ed6522 Mon Sep 17 00:00:00 2001 From: Tom Foster Date: Tue, 7 Jan 2025 23:51:14 +0000 Subject: [PATCH] Simplify caching recommendations --- proposals/4133-extended-profiles.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/proposals/4133-extended-profiles.md b/proposals/4133-extended-profiles.md index ffee37f434e..5d0fe4d05b5 100644 --- a/proposals/4133-extended-profiles.md +++ b/proposals/4133-extended-profiles.md @@ -255,11 +255,9 @@ consideration of this. - Custom fields MUST NOT trigger state events in rooms; their data MUST NOT be replicated to `m.room.member` events unless a future proposal creates exceptions for specific fields. -- Servers MAY cache remote profiles to optimise performance. Until a method for servers to notify - each other of updates is established, it is recommended that profiles be cached *no longer* than - an hour to avoid displaying stale data. If caching is implemented, servers SHOULD invalidate their - cache when receiving new profile information. A future MSC may propose a mechanism for servers to - notify each other of profile updates. +- Servers MAY cache remote profiles to optimise performance. Servers which prefer to cache details + should do so for a short period of time to avoid stale data being presented to users. + A future MSC may propose a mechanism for servers to notify each other of profile updates. - Clients MAY provide a UI for users to view and enter custom fields, respecting the appropriate namespaces.