-
Notifications
You must be signed in to change notification settings - Fork 203
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
Never return negative bump stamp #17748
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sane, even though I must admit, I don't know much about all this
# To deal with this, we just set the bump stamp to zero, which will | ||
# shove this room to the bottom of the list. This is OK as the | ||
# moment a new message happens in the room it will get put into a | ||
# sensible order again. | ||
bump_stamp = 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"new message" or "new event"? Because if it's new events, the join event will anyway generate a new positive stream ordering? (I basically know nothing about all this, I'm trying to understand :D)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically its a new "bump event", which are things like messages, stickers, etc. The idea is that we only want to "bump" the room to the top of the room list (on the client) for events of interest, and not e.g. display name changes.
synapse/synapse/types/handlers/__init__.py
Lines 28 to 36 in 5173741
SLIDING_SYNC_DEFAULT_BUMP_EVENT_TYPES = { | |
EventTypes.Create, | |
EventTypes.Message, | |
EventTypes.Encrypted, | |
EventTypes.Sticker, | |
EventTypes.CallInvite, | |
EventTypes.PollStart, | |
EventTypes.LiveLocationShareStart, | |
} |
the join event will anyway generate a new positive stream ordering?
Yeah, the membership events should always be created with a positive stream ordering. It's only if the room gets locally deleted and then rejoins the room that the local membership events would get persisted with a negative stream ordering.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the nature of #community-moderation-effort-bl:neko.dev, it basically never receives any of the above events, so it is plausible that there is a huge backfill without any bump event.
Fixes #17737