This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Allow disabled federation presence, both receiving and sending #16058
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should allow for not processing presence received over federation and also not sending it out over federation.
I have tests written for the room joining cases, I'm still working on the
regular send andreceive cases.Set in your shared configuration:
An oddity I noticed while writing some of the tests, we are queueing up presence states to send out over federation for ourselves, but they are filtered out at the federation sender level. Since that is extra traffic that goes over replication, I'll probably rip that out later on. But in the mean time, I left a comment in the one test where it'll need to be switched over to match that behavior.
Pull Request Checklist
(run the linters)
Signed-off-by: Jason Little realtyem@gmail.com