Skip to content
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

Show an error screen when the homeserver is missing MSC features #3040

Open
robintown opened this issue Mar 3, 2025 · 0 comments
Open

Show an error screen when the homeserver is missing MSC features #3040

robintown opened this issue Mar 3, 2025 · 0 comments

Comments

@robintown
Copy link
Member

We could do this to (rather forcefully) nudge homeserver admins to turn on support for delayed events.

MSCs we do care about are:

experimental_features:
    # MSC3266: Room summary API. Used for knocking over federation
    msc3266_enabled: true
    # MSC4222 needed for syncv2 state_after. This allow clients to
    # correctly track the state of the room.
    msc4222_enabled: true

# The maximum allowed duration by which sent events can be delayed, as
# per MSC4140.
max_event_delay_duration: 24h

Questions to answer:

  • Given a mismatch in required enabled MSCs do we soft-fail or hard-fail? (thinking of delayed events)
  • soft-fail candidates
    • For msc3266 this would only affect SPA guest user access.
  • hard-fail candidates
    • msc4222: hard fail since we can't guarantee proper operation
    • btw. can we also check rate limiting client side? or only in case we are running into it?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant